For me, most weeks working on Rust are fun — exhilarating, even. But, just like with anything else, some weeks are hard.
aturon.log: listening and trust, part 2
In the previous post in this series, I recounted an early lesson for the Rust Core Team about working in the open. In this post, I want to talk about the delicate interplay between listening and trust when doing design in the open.
One year of Rust | Rust Blog
Empowering everyone to build reliable and efficient software.
Announcing Rust 1.12.1 | 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.
Learning Rust
Learning Rust - Rust Programming Language Tutorials for Everyone!
The Evolution of a Rust Programmer
364 votes, 71 comments. 426K subscribers in the rust community. A place for all things related to the Rust programming language—an open-source…
Rust and the Three Laws of Informatics
Rust and the Three Laws of Informatics After 10 years in the Java world, I have recently been looking at Rust more seriously. I am barely beginning Rust programming, yet I feel enthusiastic: I …
Rust for Java developers
Introduction to the Rust programming language for java developers, (complete with code sampes) with a focus on shared concepts.
The Rust Programming Language - The Rust Programming Language
by Steve Klabnik, Carol Nichols, and Chris Krycho, with contributions from the Rust Community
Be alert: targeted attacks on prominent Rustaceans | Rust Blog
Empowering everyone to build reliable and efficient software.
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 …
Why I'm enjoying learning Rust as a Java programmer
It's been a long time since I properly learned a new language—computer or human. Maybe 25 years.
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.