Panel: What has to change to increase Rust adoption in industrial companies?
summary
Panelists list concrete blockers: managers treat Rust as a risk and ask for dollar proofs, companies need comparative experiments (two or three teams on the same product) and recruit consultants to pollinate practice, universities and interns seed adoption, and safety-critical buyers demand predictable failure modes. Examples cited include Android teams reporting gains after Rust moves, Cloudflare’s Cloudbleed turning unknown memory risk into urgent change, government pushes for memory safety, and tooling like Cargo and FerrousSystems opening industrial doors — adoption needs tailored metrics and hiring pipelines.
AI-written summary · about
chapters (21)
- 0:00Rust adoption challenges
- 1:03Managerial barriers to Rust
- 3:17Reluctance to discuss Rust
- 5:44Chasm in Rust adoption
- 7:50Unheard industrial concerns
- 11:24Managerial fears and data
- 13:30Measuring language effectiveness
- 15:15Engineers’ adoption hurdles
- 17:03Chicken-and-egg problem
- 18:06Metrics pitfalls in Rust
- 19:29Big tech vs industrial skepticism
- 21:56Tailoring Rust advocacy
- 24:24Metrics limits and persistence
- 27:58Unknown risks in safety
- 30:28Known risks over time
- 32:54Rust and developer well-being
- 33:56Hiring strategies for Rust
- 37:05Government initiatives for Rust
- 40:55Legislation shifts priorities
- 42:18Rust vs other memory-safe
- 44:04Balancing Rust advocacy
related talks
38mPanel: Rust in reality
46mPanel: Rust in Safety Critical
27mHow to (not) introduce Rust at your workplace - a tale
21mHow to Convince Your Boss to Use Rust
11mLightning Talk: The Humble Rustacean: Human Factors Behind Rust’s Success
44mPanel Discussion: Rust in the Cloud
05mBenefits and Drawbacks of Adopting a Secure Programming Language: Rust as a Case Study
13mLightning Talk: From ‘We Want Rust’ to ‘We Have a Rust Team’ — The Journey...