Alice Ryhl on Rust: why the compiler is the real safety net
Google's Alice Ryhl unpacks Rust's memory safety, ownership model, Cargo, editions, and its growing role inside the Linux kernel in this podcast deep dive.
In this episode of The Pragmatic Engineer Podcast, Alice Ryhl—a Google Android Rust team engineer and core Tokio maintainer—explains what sets Rust apart from languages like TypeScript, Go, and C++. The conversation covers how ownership and borrowing enforce memory safety, the boundaries of the unsafe keyword, Cargo's role in package management, and Rust's six-week release cadence. Ryhl argues Rust's real strength lies in catching errors at compile time rather than runtime, which makes refactoring safer and also suits AI coding agents that can iterate against compiler feedback.
The discussion also explores how Rust's edition system lets the language evolve without breaking backward compatibility, how RFC-driven governance works without a single benevolent dictator, and how Rust in the Linux kernel has recently shed its "experimental" label. Ryhl flags a risk with AI-assisted Rust: code that compiles isn't necessarily meaningful, and junior engineers may accept AI-generated Rust without understanding why the compiler approves it.
For engineers, the takeaways are practical: Rust's backend reliability case, its growing adoption in critical systems like the kernel, and its suitability for AI-assisted development make it a language worth the learning curve.