Strong software for a safer future
summary
Hospital ventilator firmware shows 22,000 versions and 963 OS updates, and real bugs cost lives and fish, so the claim is that incremental Rust tooling can stop many of those failures. Examples: use Miri to catch undefined behavior in unsafe code, run cargo-fuzz to produce panic‑causing inputs (found a real URL bug), apply formal solvers like Cary to prove no integer‑overflow panics, enable deny missing docs and clippy performance lints in CI to block unsafe or slow releases.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 4:36Software fragility in critical systems
- 7:09Why robust software matters
- 9:06Rust for safer development
- 14:14Engineering principles
- 17:50Rust as a role model
- 21:48Rust’s challenges
- 26:07Static analysis tools
- 30:52Formal methods in practice
- 34:45Safer Rust tools
- 43:31Rust’s liberating power
- 45:18Beginner-friendly tools
- 47:47Hopeful future
- 48:12Q&A
related talks
45mBuilding Safe and Secure Systems in Rust
56mRust for Safe and Scalable Automotive: Insights from
50mSmashing the Stack: Let’s Make It Less Fun And Unprofitable!
56mRust for Foundation Software
22mWriting safe and secure code
36m"Rust at the Last Mile in Healthcare"
14mAn Empirical Study of Bugs in the rustc Compiler
46mPanel: Rust in Safety Critical