Why Rust

This page is work in progress… Atm, it only contains some useful references

Why should you at least consider Rust? And why not?

Already watched and suggested for other interested people (in no specific order):

• Jon Gjenset Explains: Interview by Vitaly Bragilevsky, Head of Rust Ecosystem @ JetBrains
• When to Choose Rust • Tim McNamara • YOW! 2022
• Considering Rust - Jon Gjenset
• Living with Rust Long-Term - Jon Gjengset
• Microsoft is Getting Rusty: A Review of Successes and Challenges - Mark Russinovich
• Mark Russinovich, Microsoft Azure CTO tells Rust Nation UK 2025 why Azure is moving to Rust from C++
• Lars Bergstrom - Beyond Safety and Speed: How Rust Fuels Team Productivity
• Spreading Rust to the rest of the company: Moving past the proof of concept - Tim McNamara
• The promise of Rust - fasterthanlime
• 10 Reasons Not To Use Rust (The Whole Truth) - fasterthanlime
• C++ vs Rust: which is faster?

To be properly watched:

• Actuate 2025: End to End Robotics in Rust with Vivek Bagaria
• Rust Adoption At Scale with Ubuntu - Jon Seager

References

• The Rust Programming Language Book: The main introductory book about Rust, usually referred to as “the book” by rustaceans
• The rustc book: The compiler for the Rust programming language, provided by the project itself. It also comes with its own set of lints.
• Clippy Documentation: A collection of lints to catch common mistakes and improve your Rust code. It is a superset of rustc lints.
• Rust by Example: a collection of runnable examples that illustrate various Rust concepts and standard libraries. Usually consumed alongside “the book”, gives a more interactive experience to learning Rust basics
• The Rust Reference: a book that serves as a reference to what is available in stable Rust.
• The Rust Standard Library Documentation
• crates.io: The Rust community’s crate registry
• The Cargo book: cargo is the Rust package manager and build system
• The rustdoc Book: The standard Rust distribution ships with a tool called rustdoc. Its job is to generate documentation for Rust projects.
• Rust API Guidelines: This is a set of recommendations on how to design and present APIs for the Rust programming language. They are authored largely by the Rust library team, based on experiences building the Rust standard library and other crates in the Rust ecosystem
• Command Line Applications in Rust: Rust is a statically compiled, fast language with great tooling and a rapidly growing ecosystem. That makes it a great fit for writing command line applications: They should be small, portable, and quick to run. Command line applications are also a great way to get started with learning Rust; or to introduce Rust to your team!