mqttrs VS calloop

I saw options like https://github.com/00imvj00/mqttrs and https://github.com/zonyitoo/mqtt-rs - they are compiling for wasm, but for my understanding they are just packet decoders/encoders - so all state machines etc I should write myself. Maybe there are creates that are network agnostic, meaning I will feed it bytes, it will feed me bytes back and all I need to do is to send them?

What I really want though, is a simple MQTT abstraction around a socket that I can use in non-blocking mode and put into an event loop like calloop. There's mqttrs for the protocol-only part, but I'll still need to convince my employer that it's worth it to implement the IO for it from scratch.

I've used and contributed to mqttrs, as I needed more low-level control than what rumqtt provides and was keen on using pure Rust. I had to pause my MQTT project two years ago, but AFAICT mqttrs is still a solid option.

What are the best crates for mqtt these days? I found mqtt-rs which looks pretty promising - are there any other ones I should be aware of?

calloop smell good. look close calloop

What I really want though, is a simple MQTT abstraction around a socket that I can use in non-blocking mode and put into an event loop like calloop. There's mqttrs for the protocol-only part, but I'll still need to convince my employer that it's worth it to implement the IO for it from scratch.

You may be interested in calloop, which is what backs the Smithay compositor (and also the winit event loop, at least on the Wayland backend). It's basically this crate, but with a handful more batteries included.