rfc-leadership-council VS rumqtt

This fork promises "All of the memory-safe features you love, now with 100% less bureaucracy!" Compelling, until you realise that all the commits are auto-merges of rust-lang/rust's main branch. Which means the same teams doing the same work, under a different name.

Rust is experiencing growing pains because they're still figuring out a governance structure that works for everyone. They want to simultaneously keep the current structure of bottom up development where each team (compiler, lang, crates.io, cargo) has the autonomy to make decisions for themselves, but the project as a whole can speak can come to a consensus and speak with a single voice. That's what this RFC tries to capture (https://github.com/rust-lang/rfc-leadership-council/blob/mai...). But the project isn't there yet, and is making these frustrating missteps in the interim. The lack of transparency into these missteps manifests as "bureaucracy" to outsiders like us.

If Crab lang actually attracted people doing the real work of development, they would have the exact same "bureaucracy" as teams tried to figure out how to build consensus and speak with one voice. The fact that they don't have bureaucracy is a direct consequence of them not doing any work right now. None of the people involved in regular Rust work, as far as I can tell, so they might not be aware of this.

Lastly, I want to note that the top comment in this thread is blaming the Foundation, which is simply bizarre. The Foundation very explicitly tries to stay hands off on technical decisions and does not interfere in how the teams organise themselves. You may disagree with that, but it's an inaccurate characterisation.

Read eg. https://github.com/rust-lang/rfc-leadership-council/blob/main/text/3392-leadership-council.md as start

https://github.com/bytebeamio/rumqtt

Disclaimer: have not tried it myself. I was, however, considering using it to replace Mosquitto as a broker.

Other crates like https://crates.io/crates/paho-mqtt and https://github.com/bytebeamio/rumqtt are not available for browsers and do not compile to wasm.

Recently lot of new contributors showed interest, as well as contributed to rumqtt, so thank you so much everyone for your support <3 Feel free to discuss anything in comments, if you wish to contribute as well, you can look for `good-first-issues` ( or open new issues here )

GitHub release - rumqttd-0.15.0

there is already an issue open for it: https://github.com/bytebeamio/rumqtt/issues/432. It is something that we would love to have, but not something in priority.

I wanted to let you know that rumqttc, a Rust MQTT client library, now supports several new features in MQTT 5 protocol. If you're not familiar with MQTT, it's a lightweight messaging protocol designed for IoT devices with limited resources.

I know I should have asked this in their issues, but someone already did and didn't get a response. So I was not sure whether to create another issue, or comment in the same one (and not get a response as well?). So I decided to ask on Reddit first, thank you! https://github.com/bytebeamio/rumqtt/issues/598