C++ Should Be C++
summary
Stack Overflow data shows Rust use among C++ developers rising from ~5% in 2009 to >20% of C++ devs use Rust by 2023, an Android study reports fewer vulnerabilities after migration, and one game studio abandons a three‑year Rust effort for practical reasons. Committee growth creates incoherence with concrete failures: simd equality breaks regularity, thread attributes slip into heavy template magic, and sender/receiver designs become unreadable. The Beamman project prototypes standard‑library proposals with runnable docs and simple builds to improve proposal quality.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:24Rust push and memory safety
- 10:20C++ vs Rust popularity
- 25:14Why C is still popular
- 34:56C++ in the toolbox
- 47:08Committee complexity risks
- 1:06:46Complexity and incoherence
- 1:11:03Beaman project hope
- 1:28:27Q&A
related talks
41mC++ Migration Strategies
05mBenefits and Drawbacks of Adopting a Secure Programming Language: Rust as a Case Study
30mBack to the Future: Rust, Zig, and the New Age of C++ Alternatives
21mRust - Cargo Cult?
01h 37mC++ And Beyond: Discussion
01h 34mC++11/14 at Scale - What Have We Learned?
50mSmashing the Stack: Let’s Make It Less Fun And Unprofitable!
01h 08mFireside chat