C++ ecosystem: For better, for worse
summary
JetBrains survey of ~1,700 primary C++ developers finds slow standard adoption, with a big cohort still on C++11 and 46% using C++17 while students move faster than industry. Tooling use is patchy: clang-tidy/clangd and IDE checks are common, Google Test and Catch lead unit testing, yet many projects run no unit tests and 84% of embedded projects lack unit testing. Embedded is vendor-locked (macros, SDKs); games use Unreal-style macro reflection and custom allocators.
AI-written summary · about
chapters (32)
- 0:00Introduction
- 2:13Agenda
- 4:12State of developer ecosystem survey
- 9:47Simple Class Foundation survey
- 10:50Audience
- 13:18Employment status
- 14:10Questions
- 14:40Question Results
- 15:37Comparison with 2018
- 16:57Comparison with 2019
- 17:38Standard distribution
- 19:22Standard slices
- 19:59Platform slices
- 21:19Areas of development
- 22:04Employment groups
- 23:49Upgrading
- 24:08Plans to upgrade
- 26:56C Perl
- 27:18Financial
- 27:58C choices
- 28:33Performance
- 31:31C usage
- 33:42Embedded
- 34:31Certification
- 37:25Macros
- 41:26Language Choices
- 44:49Usage
- 45:42Reflection
- 49:51Customer locations
- 53:58Testing tools
- 56:00Unit testing frameworks
- 57:29Google test and Boost test
related talks
58mC++ ecosystem: the renaissance edition
53mStandard C++ Toolset
01h 32mClosing Keynote: C++ Development Tools: Past, Present and Future
01h 34mC++11/14 at Scale - What Have We Learned?
57mThe Real Problem of C++
54mA look at C++ through the glasses of a language tool
01h 11mC++ in the World of Embedded Systems
19mThe Badlands of C++: Professional Game Development