The Real Problem of C++
summary
Argues the real problem is people not the language: widespread projects still use legacy patterns so safety features sit unused, creating a guessed 10% bubble of up‑to‑date C++ users. Demonstrates concrete fixes: replace index-heavy loops with ranges (example: rewriting “print five biggest countries”), catch undefined behavior by running logic in constexpr (compile‑time static_assert), and eliminate lifetime/type bugs with strong types and value semantics (variant replacing visitor). Cites view counts (~178k) as evidence few reach modern practices and urges adoption of these tools.
AI-written summary · about
chapters (17)
- 0:00C++ safety problem
- 1:20Why C++ is unsafe
- 3:04Performance focus in C++
- 6:56Four horsemen of C++
- 7:17Bound safety and raw loops
- 13:16Modern C++ with ranges
- 17:56Undefined behavior checks
- 24:42Type safety with strong types
- 33:59Performance impact of strong types
- 34:21Lifetime safety and value semantics
- 41:25Visitor pattern with value semantics
- 43:31Mindset and people issues
- 46:47Switching to Rust?
- 48:34Teaching modern C++ safely
- 51:47Improving safer C++ adoption
- 53:12Summary and call to action
- 53:34Q&A: Tooling and future
related talks
01h 28mKeynote: Safety, Security, Safety and C / C++ - C++ Evolution
01h 01mThe Best Parts of C++
01h 01mLearning (and teaching) modern C++ - Challenges and Resources
01h 02mC++ Today: The Beast is Back
01h 25mComparing 'Classic C++' and 'Modern C++' Ways to Solve Programming Tasks
01h 01mSome Programming Myths Revisited
14mEmbedded C and C++: A Security Perspective
54mTypical C++, But Why?