Why Rust is different, with Alice Ryhl
<p><strong>Brought to You By:</strong></p><p><strong>• </strong><a target="_blank" href="https://antithesis.com/pragmatic"><strong>Antithesis</strong></a> – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages.</p><p><strong>• </strong><a target="_blank" href="https://sentry.io/pragmatic"><strong>Sentry</strong></a><a target="_blank" href="https://sentry.io/pragmatic"></a> – application monitoring software considered “not bad” by millions of developers</p><p>• <a target="_blank" href="https://craft-conf.com/2026"></a><a target="_blank" href="https://craft-conf.com/2026"><strong>Craft Conference</strong></a><a target="_blank" href="https://craft-conf.com/2026"></a>: join Gergely, Kent Beck, Hillel Wayne and others at the conference dedicated to the art and science of software delivery craft.</p><p>—</p><p>Rust is one of the most admired programming languages around – and also one of the hardest to learn. What makes developers stick with it?</p><p>In this episode of The Pragmatic Engineer Podcast, I sit down with Alice Ryhl, a software engineer on Google’s Android Rust team, and a core maintainer of Tokio, which is the most widely-used async runtime in Rust.</p><p>We discuss what makes Rust different from other languages like TypeScript, Go, and C++, and why so many developers say that “once it compiles, it works.” We go deep into memory safety, ownership, borrowing, unsafe Rust, and Cargo.</p><p>We also cover how Rust is governed by RFCs, feature flags, its six-week release cycle, how engineers get paid to work on the language, and also look into how Rust’s use inside the Linux kernel is progressing.</p><p>—</p><p><strong>Timestamps</strong></p><p>(00:00) Intro</p><p>(04:09) Tokio: an overview</p><p>(05:11) What Alice likes about Rust</p><p>(12:48) Rust for TypeScript engineers</p><p>(13:51) Moving from C++ to Rust</p><p>(14:34) Memory safety</p><p>(18:12) Garbage collection tradeoffs</p><p>(21:46) Ownership, references, and borrowing</p><p>(26:59) Unsafe in Rust</p><p>(31:21) Crates and Cargo</p><p>(35:55) Language design and RFCs</p><p>(43:02) Building new features</p><p>(46:30) Editions vs. versions</p><p>(49:47) Getting paid to work on Rust</p><p>(51:27) Contributing to Rust</p><p>(53:03) Rust in the Linux kernel</p><p>(55:45) AI use cases for Rust</p><p>(1:01:35) Learning Rust</p><p>(1:03:54) Book recommendation</p><p>—</p><p><strong>The Pragmatic Engineer deepdives relevant for this episode:</strong></p><p><strong>• </strong><a target="_blank" href="https://newsletter.pragmaticengineer.com/p/the-past-and-future-of-backend-practices">The past and future of modern backend practices</a></p><p><strong>• </strong><a target="_blank" href="https://newsletter.pragmaticengineer.com/p/the-programming-language-after-kotlin">How Kotlin was built</a> with Andrey Breslav</p><p><strong>• </strong><a target="_blank" href="https://newsletter.pragmaticengineer.com/p/from-swift-to-mojo-and-high-performance">How Swift was built</a> with Chris Lattner</p><p><strong>• </strong><a target="_blank" href="https://newsletter.pragmaticengineer.com/p/how-linux-is-built-with-greg-kroah">How Linux is built</a> with Greg KH</p><p>—</p><p>Production and marketing by <a target="_blank" href="https://penname.co/"></a><a target="_blank" href="https://newsletter.pragmaticengineer.com/p/engineers-leading-projects">https://penname.co/</a>. For inquiries about sponsoring the podcast, email [email protected].</p> <br/><br/>Get full access to The Pragmatic Engineer at <a href="https://newsletter.pragmaticengineer.com/subscribe?utm_medium=podcast&utm_campaign=CTA_4">newsletter.pragmaticengineer.com/subscribe</a>