
The Pragmatic Engineer Why Rust is different, with Alice Ryhl
291 snips
May 20, 2026 Alice Ryhl, a Google Android Rust engineer and Tokio maintainer, discusses what makes Rust unique. Short, punchy takes on ownership, the borrow checker, unsafe blocks, Cargo and crates, async runtimes, kernel adoption, governance via RFCs, and how Rust compares to TypeScript, Go and C++.
AI Snips
Chapters
Books
Transcript
Episode notes
Memory Safety Eliminates Common Security Holes
- Memory safety in Rust prevents a whole class of bugs that commonly become security vulnerabilities in C and C++.
- Examples include off-by-one reads, use-after-free, and memory reuse leading to privilege escalations in kernels.
Unsafe Is A Scoped Escape Hatch For Low Level Work
- unsafe in Rust is an explicit, scoped escape hatch that allows low-level operations but keeps most safety checks intact.
- Encapsulate unsafe inside safe APIs (e.g., implementing a Vec or FFI) so callers remain in safe Rust while internals use unchecked operations.
Treat Cargo As Your All In One Tool
- Use Cargo as your single local tool for building, testing, running docs, and managing dependencies.
- Cargo stores downloaded crates in a shared registry cache and keeps builds local to the project, avoiding global installs.







