Fireside chat
summary
History of Rust traces concrete choices: adoption of explicit lifetimes evolving into non-lexical lifetimes to handle lookup/mutation patterns, planning Polonius for the remaining cases, and keeping fine-grained unsafe code guidelines rather than whole-function unsafe. The ecosystem proves partial rewrite strategy works—Dropbox reduced infra cost by rewriting a component in Rust; kernel and curl efforts are underway. Tooling focuses on runtime checks and models: the Miri interpreter (dynamic checking of MIR) and memory-model work aim to validate unsafe blocks before trust.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:28Introducing the speakers
- 4:01What is Rust
- 10:08Why systems languages
- 16:00Rust
- 24:02Prehistory
- 28:39Memory management
- 36:29Unsafe code
- 38:58C code
- 41:42Code guidelines
- 48:09Rust pain points
- 53:29Other sources of inspiration
- 59:33What does safe mean
related talks
21mRust - Cargo Cult?
26mMoving to modern languages in long-living projects
25m"Eternal Sunshine of the Rustfmt'ed Mind"
05mBenefits and Drawbacks of Adopting a Secure Programming Language: Rust as a Case Study
46mThoughtful Software Engineering
06mLayered Configuration and Safe Hot Reload in Rust
50mSmashing the Stack: Let’s Make It Less Fun And Unprofitable!
01h 29mC++ Should Be C++