Our great sponsors
rumqtt | rfcs | |
---|---|---|
34 | 666 | |
1,473 | 5,700 | |
4.6% | 1.4% | |
8.9 | 9.8 | |
9 days ago | 5 days ago | |
Rust | Markdown | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rumqtt
-
New scalable, fault-tolerant, and efficient open-source MQTT broker
https://github.com/bytebeamio/rumqtt
Disclaimer: have not tried it myself. I was, however, considering using it to replace Mosquitto as a broker.
-
What MQTT crates for use in WASM are out there?
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.
- Announcing rumqttd v0.18.0: with improved performance and reduced binary size due to enhanced release profile, while featuring retained and will messages, will delay interval for MQTTv5 and other cool changes!
- Announcing rumqttd v0.17.0 with Shared Subscriptions and Subscription IDs adding up to better MQTTv5 support!
-
rumqttd now supports QoS2 and MQTT over websockets
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 )
- Rumqttd now supports MQTTv5 topic alias and message expiry
-
Announcing rumqttd v0.15.0 with MQTTv5 features like Topic Alias and Message Expiry
GitHub release - rumqttd-0.15.0
-
rumqttc 0.21.0 released with MQTT5 support
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.
-
Hey Rustaceans! Got a question? Ask here (15/2023)!
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
rfcs
-
Ask HN: What April Fools jokes have you noticed this year?
RFC: Add large language models to Rust
https://github.com/rust-lang/rfcs/pull/3603
- Rust to add large language models to the standard library
-
Why does Rust choose not to provide `for` comprehensions?
Man, SO and family has really gone downhill. That top answer is absolutely terrible. In fact, if you care, you can literally look at the RFC discussion here to see the actual debate: https://github.com/rust-lang/rfcs/pull/582
Basically, `for x in y` is kind of redundant, already sorta-kinda supported by itertools, and there's also a ton of macros that sorta-kinda do it already. It would just be language bloat at this point.
Literally has nothing to do with memory management.
- Coroutines in C
-
Uv: Python Packaging in Rust
Congrats!
> Similarly, uv does not yet generate a platform-agnostic lockfile. This matches pip-tools, but differs from Poetry and PDM, making uv a better fit for projects built around the pip and pip-tools workflows.
Do you expect to make the higher level workflow independent of requirements.txt / support a platform-agnostic lockfile? Being attached to Rye makes me think "no".
Without being platform agnostic, to me this is dead-on-arrival and unable to meet the "Cargo for Python" aim.
> uv supports alternate resolution strategies. By default, uv follows the standard Python dependency resolution strategy of preferring the latest compatible version of each package. But by passing --resolution=lowest, library authors can test their packages against the lowest-compatible version of their dependencies. (This is similar to Go's Minimal version selection.)
> uv allows for resolutions against arbitrary target Python versions. While pip and pip-tools always resolve against the currently-installed Python version (generating, e.g., a Python 3.12-compatible resolution when running under Python 3.12), uv accepts a --python-version parameter, enabling you to generate, e.g., Python 3.7-compatible resolutions even when running under newer versions.
This is great to see though!
I can understand it being a flag on these lower level, directly invoked dependency resolution operations.
While you aren't onto the higher level operations yet, I think it'd be useful to see if there is any cross-ecosystem learning we can do for my MSRV RFC: https://github.com/rust-lang/rfcs/pull/3537
How are you handling pre-releases in you resolution? Unsure how much of that is specified in PEPs. Its something that Cargo is weak in today but we're slowly improving.
- RFC: Rust Has Provenance
-
The bane of my existence: Supporting both async and sync code in Rust
In the early days of Rust there was a debate about whether to support "green threads" and in doing that require runtime support. It was actually implemented and included for a time but it creates problems when trying to do library or embedded code. At the time Go for example chose to go that route, and it was both nice (goroutines are nice to write and well supported) and expensive (effectively requires GC etc). I don't remember the details but there is a Rust RFC from when they removed green threads:
https://github.com/rust-lang/rfcs/blob/0806be4f282144cfcd55b...
-
Why stdout is faster than stderr?
I did some more digging. By RFC 899, I believe Alex Crichton meant PR 899 in this repo:
https://github.com/rust-lang/rfcs/pull/899
Still, no real discussion of why unbuffered stderr.
- Go: What We Got Right, What We Got Wrong
-
Ask HN: What's the fastest programming language with a large standard library?
Rust has had a stable SIMD vector API[1] for a long time. But, it's architecture specific. The portable API[2] isn't stable yet, but you probably can't use the portable API for some of the more exotic uses of SIMD anyway. Indeed, that's true in .NET's case too[3].
Rust does all this SIMD too. It just isn't in the standard library. But the regex crate does it. Indeed, this is where .NET got its SIMD approach for multiple substring search from in the first place[4]. ;-)
You're right that Rust's standard library is conservatively vectorized though[5]. The main thing blocking this isn't the lack of SIMD availability. It's more about how the standard library is internally structured, and the fact that things like substring search are not actually defined in `std` directly, but rather, in `core`. There are plans to fix this[6].
[1]: https://doc.rust-lang.org/std/arch/index.html
[2]: https://doc.rust-lang.org/std/simd/index.html
[3]: https://github.com/dotnet/runtime/blob/72fae0073b35a404f03c3...
[4]: https://github.com/dotnet/runtime/pull/88394#issuecomment-16...
[5]: https://github.com/BurntSushi/memchr#why-is-the-standard-lib...
[6]: https://github.com/rust-lang/rfcs/pull/3469
What are some alternatives?
ntex-mqtt - MQTT Client/Server framework for v5 and v3.1.1 protocols
rust - Empowering everyone to build reliable and efficient software.
mqtt-broker - A tokio-based MQTT v5 broker written in pure Rust [WIP]
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
mqtt-rs - MQTT protocol library for Rust
crates.io - The Rust package registry
mosquitto - Eclipse Mosquitto - An open source MQTT broker
polonius - Defines the Rust borrow checker.
futures-batch - An adapter for futures, which chunks up elements and flushes them after a timeout — or when the buffer is full. (Formerly known as tokio-batch.)
Rust-for-Linux - Adding support for the Rust language to the Linux kernel.
lora-rs - LoRa and LoRaWAN crates for End Devices
rust-gc - Simple tracing (mark and sweep) garbage collector for Rust