Panel: Rust in Safety Critical
summary
Panel documents concrete hurdles and wins: Rust’s type system enables easier formal verification and the community treats unsafe as a manageable, reviewable exception; education and legacy expertise are the biggest adoption blockers, not language soundness; supply‑chain and liability problems mean crates.io cannot certify safety and organizations prefer contractual control; practical tooling mentioned includes cargo deny, OpenSSF scorecards and Eclipse TSF; firms run six‑hour Rust intro courses and sometimes rework or vendor and vendor‑lock binary deliveries to meet safety processes.
AI-written summary · about
chapters (9)
- 0:00Welcome to Rust safety panel
- 1:48Defining safety in software
- 5:19Rust’s safety advantages
- 8:12Gaps and roadblocks in Rust
- 13:03Debunking Rust’s learning curve
- 21:08Open source in safety systems
- 32:31Role of unsafe in Rust
- 35:49Open source safety practice
- 45:22Closing thoughts & Q&A
related talks
46mPanel: What has to change to increase Rust adoption in industrial companies?
38mPanel: Rust in reality
56mRust for Foundation Software
22mRust as a Foundation for a Safe and Sustainable Future
45mBuilding Safe and Secure Systems in Rust
11mLightning Talk: The Humble Rustacean: Human Factors Behind Rust’s Success
07mLightning Talk: “How Rust Is Steering Automotive Software Toward Safety”
58mRust for The Curious C++ Developers