Rust has one serialization library that is Serde. Over the years I collected a bucket list of all the things that I do not enjoy about it. Finally did something about it and finished Deser. Here is a small summary of the why, what and how: https://t.co/g4qUYB0M8G
Supporting native Rust in Workers with the new Emscripten target for wasm-bindgen
> Cloudflare adds experimental Emscripten support for Rust Workers, enabling Tokio, native sockets, and complex Rust applications like Minecraft servers.
Topcoat is pushing the boundary of server applications with Rust. Given the discussion falling out from @dhh's keynote, I thought I would write a bit about why I'm working on Topcoat and the cool features that were recently shipped: https://t.co/QGPw271q3l
Principles for fast Tokio applications
> Measure real metrics first. Yield for latency, batch for throughput. Avoid contended mutexes, global resources, and unbounded parallelism on Tokio.
JUST IN: Dioxus Labs is joining Cognition
> Dioxus Labs joins Cognition to accelerate Devin; team continues developing Dioxus, Blitz, Taffy, and Subsecond without monetization pressure.
How we developed the world's first safety-certified product written in Rust – and why we went bare metal
> Sonair certified ADAR One, the first safety-critical embedded system in Rust, using Ferrocene on bare-metal TI Sitara for robot safety sensors.
How we saved 100 terabytes of memory by optimizing 1.1.1.1’s DNS cache
> Cloudflare cut 1.1.1.1’s DNS cache memory over 50% via five Rust optimizations, freeing 100 TB while boosting speed.
https://t.co/j9Aj88KEnC
Atuin's sync is now 32x faster.
Thousands of records in single digit seconds.
The hard part: Atuin is end-to-end encrypted. The server can't read, compress, or bundle your data, so every trick a normal sync server uses is off the table.
Here's how we did it anyway 🧵
usage-rs (my blazing fast rust cli framework) is ready for testing! ~2500x faster than clap!
It’s mostly clap-compatible, but uses a serde-like architecture: your CLI is compiled into a static command map instead of rebuilding a command tree every time the program starts.
- config-file and env var integration
- negatable flags (--color/--no-color)
- expression based validation
- resolves clap's most upvoted issues
- smaller binary size: 1.5mb (usage-rs) vs 3.1mb (clap)
- NO THIRD PARTY CRATES! (except proc-macro2)
- includes advanced completion and docs generation like my clis all have (usage-cli is not required for end users anymore!)
it's experimental so there may be breaking changes in point releases for now. If you try it out, I'd love it if you could have your agent send me a summary of how well or not so well it went as a gh discussion.
https://t.co/OTCCGh6UoE
Came across a Rust LSP that stays under 100MB of RAM, and instantly resumes indexing after restart. 🦀
Rust Glancer is a 4-month-old alternative to rust-analyzer, built by a 7-year Rust veteran who's contributed to rustc, clippy, and rust-analyzer itself.
The motivation was blunt: running two IDEs side by side, rust-analyzer was eating 16GB of RAM, and every editor restart meant re-indexing from scratch.
The architectural bet is the interesting part. rust-analyzer uses an incremental, always-in-memory query database (salsa) to stay fast on every keystroke. Rust Glancer does the opposite: it freezes a full analysis to disk, only loads what a query actually needs, and reuses that saved index across restarts.
The tradeoff is real : new items aren't indexed until you save, and it's inherently slower than true incremental analysis. But in early benchmarks it's actually indexing faster than rust-analyzer on both a 2025 M4 Max and a 2020 M1 8GB machine, while using a fraction of the memory.
Worth noting directly: the author is fully transparent that this was built with heavy LLM use, every PR reviewed and understood, not vibe-coded. Given the Rust project just published its own LLM policy, this feels like a real, honest example of what disclosed, reviewed AI-assisted development actually looks like in practice.
Still incomplete : no proc macro support, some missing LSP actions, but already usable as a daily driver, with a VS Code extension available today.
🔗 https://t.co/VqBR53qKP7
#RustLang #DevTools #LSP #OpenSource #AI
I have accepted reality, I no longer write code manually.
But man do I miss reading a bug report and knowing exactly off the top of my head the if statement that causes it in the exact file in a 100K+ line codebase.
When does rewriting in Rust actually make sense? 🦀
Marek Grzelak and Mateusz Maćkowski, creators of https://t.co/91tePBy9U5 looked beyond the RIIR meme at real projects: performance gains, memory safety, new bugs, abandoned rewrites, and Rust’s growing role in Linux and Windows.
Read the full post to find out 👇
https://t.co/cQOUXCx87W
herdr is 105 days old.
i started writing a 10,000 github stars celebration post. before i finished it, we passed 12,500!
on june 30, herdr hit #1 on github trending. it has stayed in the top 10 since.
i’ve been building it solo and full-time, in public from day one: roadmap, issues, feature requests, releases.
so instead of just celebrating, i’m opening the stats too: stars, downloads, website traffic, releases, and where the numbers come from.
https://t.co/MeA1u4yIII
thank you for being part of the herd 🐑
Rust in space 🚀
Gama builds satellites in Rust.
I talk with Sebastian Scholz in the final episode of Season 5 of Rust in Production.
Topics: defensive programming, design patterns, testing, and more!
Link: https://t.co/rKrVjN0o8A
#rust#space
🦀 Best Rust learning strategy: read great code
This code-dive on uv (Python pkg manager) OnceMap shows how real-world async Rust avoids duplicate work:
• DashMap for concurrency
• Notify to park/wake waiters
• race fixed with pin!
https://t.co/SYOlDY9VEp
#rust#rustlang
Radar replaced their Elasticsearch/MongoDB-based geospatial search backend with a single Rust binary.
Here's their story: https://t.co/ek74qqoPnI
Thanks to @j_ckao for the interview!
#rustlang#rust#rustinproduction
🦀 Stop forwarding Rust errors.
Rust type system is your ally for building errors that are verbose, debuggable, and actionable.
thiserror + anyhow are great for quick prototypes, but they can tempt you to skip adding real context.
https://t.co/NduIGGSOEI
#rust#rustlang