C++ ecosystem: the renaissance edition
summary
Independent surveys show C++ usage is fragmented: JetBrains collects ~19,000 replies with ~1,800 C++ respondents, and the ISO C++ Foundation survey has ~1,000 respondents; 41% on C++17 and about 12% on C++20 in the JetBrains data. Major pain points are concrete: managing libraries and build systems, long build times and CI pipelines, and spotty tooling support. Tool adoption specifics: Google Test and Catch2 lead unit testing, CMake dominates builds, Conan/vcpkg and manual vendoring split dependency management, and ~35% report no static analysis while ~46% rely on IDE-integrated checks.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:36Anastasiias background
- 2:06Agenda
- 2:28Macros
- 4:47Overloads
- 7:41Reload operators
- 11:33Common style
- 13:37Hirums law
- 14:43Cognitive overhead
- 24:08Survey results
- 29:12Challenges of moving to a new standard
- 31:48Risks of moving to new standards
- 34:53Unit tests
- 37:21Static analysis tools
- 41:10Managing dependencies
- 45:17Measure picking points
- 45:37Top usage areas
- 46:04Financial
- 51:21Gate Castle
- 55:07Conclusion
related talks
01h 22mC++ ecosystem: For better, for worse
53mStandard C++ Toolset
57mKeynote: How To Address 7 Major C++ Pain Points with Tools
18mKeynote Session Preview - C++ Painkillers
18mKeynote Session Preview - C++ Painkillers
01h 32mClosing Keynote: C++ Development Tools: Past, Present and Future
57mThe Real Problem of C++
01h 02mC++ Today: The Beast is Back