I think the Rust RFC process needs serious reform. In this blog post, I'll explain why I think that, by covering some of the problems with the current process. Before I get all negative, I think RFCs are amazing! They've been a crucial part of Rust's open design and community-focussed
Refining Rust's RFCs · Aaron Turon
At the heart of Rust’s open development is the RFC process. Every major change to the language, compiler, core libraries, tooling, and policy go through an RFC writeup and consensus-building process. The process served us incredibly well in clarifying our technical direction on the road to 1.0, and has continued to be highly active since then, with on average about 2 RFCs merged every week.
rfcs/text/0000-roadmap-2017.md at roadmap-2017 · aturon/rfcs
RFCs for changes to Rust. Contribute to aturon/rfcs development by creating an account on GitHub.
How to Read an RFC
Requests for Comments (RFCs) are how we specify many protocols on the Internet. These documents are alternatively treated as holy texts by developers who parse them for hidden meanings, then shunned as irrelevant because they can’t be understood. This often leads to frustration and – more significantly – interoperability and security issues. However, with some insight into how they’re constructed and published, it’s a bit easier to understand what you’re looking at.
One year of Rust | Rust Blog
Empowering everyone to build reliable and efficient software.
rust-lang/rust is adopting an LLM policy | Inside Rust Blog
Want to follow along with Rust development? Curious how you might get involved? Take a look!
Rust in 2021
This is my response for this year's call for blog posts. I am writing this as a language implementor, not as a language user. I also don't try to prioritize the problems. The two things I'll mention are the things that worry me most without reflecting on the overall state of the project. They are not necessary the most important things.
Are we observable yet? An introduction to Rust telemetry
Hands-on technical leader, Rust expert.
Proposal for a staged RFC process · baby steps
This blog is where I post up various half-baked ideas that I have.
rfcs/atproto/001-private-content.md at main · knasher/rfcs
Technical RFCs and design proposals for protocols and systems - knasher/rfcs
Rust for Java Devs
I’d like to take a change for this blog and leave the more bleeding edge topics to focus on perhaps one of the most important things one can do in the Rust community: teaching new Rust …
Be alert: targeted attacks on prominent Rustaceans | Rust Blog
Empowering everyone to build reliable and efficient software.
An early look at tailscale-rs, a tsnet library in Rust
We've launched an experimental Rust library for Tailscale via tsnet. Help test tailscale-rs and shape it with your feedback.
How Our Rust-to-Zig Rewrite is Going
For the past year and a half, the team building Roc's compiler has been rewriting our 300,000 lines of Rust code into Zig, for reasons I'll recap below. We recently passed an exciting milestone: feature parity with the original compiler!
Announcing Rust 1.12.1 | Rust Blog
Empowering everyone to build reliable and efficient software.