Our great sponsors
-
git-repo-language-trends
Analyze programming language usage over time in a git repository and produce a graphical or textual representation of the result.
-
rust-esp32-std-demo
Rust on ESP32 STD demo app. A demo STD binary crate for the ESP32[XX] and ESP-IDF, which connects to WiFi, Ethernet, drives a small HTTP server and draws on a LED screen.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
I originally wrote https://github.com/Enselic/git-repo-language-trends in Rust but had to switch to Python due to the immature plotting library ecosystem in Rust, at the cost of 7 times slower performance.
I don't know if the ESP experience was recent, but I'd like to mention https://github.com/ivmarkov/rust-esp32-std-demo
Not quite the same scenario but I'm rewriting a parser written with nom into a C# library with Pidgin. The Rust version was written for use within another CLI tool and nom made writing parsers really easy but I need to be able to consume the same features in a larger C# project and it was easier to rewrite than to wrangle the Rust API into #[repr(C)].
Not quite the same scenario but I'm rewriting a parser written with nom into a C# library with Pidgin. The Rust version was written for use within another CLI tool and nom made writing parsers really easy but I need to be able to consume the same features in a larger C# project and it was easier to rewrite than to wrangle the Rust API into #[repr(C)].
Just adding an example to the other side, I wrote https://rustpad.io/ in Rust, which is a collaborative text editor that uses WebSockets and resolves edit conflicts in real time using an operational transformation algorithm. It's a fairly complex bit of logic. But I actually thought Rust was the best language for this application because of performance, data race-safety, Serde, and the borrow checker. (My second choice would have been Go with stress tests run under `the -race flag.)
The link to the espressive issue trackers: https://github.com/espressif/llvm-project/issues/4