Like last year, the Rust community team asked community members to write blog posts "proposing goals and directions for 2019"; this is mine. Like withoutboats' post and Niko Matsakis' take, this post will focus on organizational issues. As such, the "ownership" from the title refers to a leadership principle, not the technical type system concept we all know and love.
Ownership is a fundamental piece of Rust’s story. It amounts to a tight set of rules about who owns a value in a program, how that value can be aliased and mutated, and when that value is dropped. It prevents shared mutable state, which is the root cause of major bugs in software written without the same guarantees.
Rust Governance: Scaling Empathy
There’s been a lot of talk about improving Rust’s governance model lately. As we decompress from last year’s hectic edition work, we’re slowly starting to look at all the bits of debt we accumulated …
Rust is not a Company
Last year, as an occasional contributor to the Rust project, I did not think much about the organisational structure of the team behind the project. I saw a hierarchy of teams and groups, team leaders, etc. Just like any other organisation. This year, after getting more involved, becoming a library team member and eventually team lead, I spent some more time thinking about why we have this structure, what these teams are for.
One year of Rust | Rust Blog
Empowering everyone to build reliable and efficient software.
Announcing Rust 1.96.1 | Rust Blog
Empowering everyone to build reliable and efficient software.
Rust's Most Unrecognized Contributor
I think the Rust language is a big success. When I think back on it I am in awe: so much had to go right to get where we are, and there were so many opportunities to go wrong. It took many tiny miracles for the Rust language to become what it has. Those miracles didn’t happen by accident though: each one was created by a real person, and real people orchestrated them to become something great.
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.
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!
Growing the Rust Community
The Rust community and its commitment to advancing the Rust language are the topics of the fifth video in our series about the Rust…
Announcing Rust 1.12.1 | Rust Blog
Empowering everyone to build reliable and efficient software.
Shar: One year with Rust.
137 votes, 28 comments. Hi, Reddit! I posted here for a few times, and now our team has reached the important stage of development - we are launching…
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 …
Rust's Golden Rule
I find myself thinking about a particular design principle of Rust today. I’m not sure I’ve ever seen it named specifically before, but it gets referred to from…
Here's my plan to save Twitter: let's buy it | Nathan Schneider
Corporate sharks are circling around the platform we love. But there is another way: shared ownership, where the community takes control
Introducing the Ownership Model Canvas
A new tool to re-align business success with ownership
