Modern C++ Coming to Terms With Terms
summary
Argues that C++11 is a hard boundary: code before 2011 is classic C++ and code from C++11 onward is modern C++, because the committee shifts releases from a 13-year gap to a three-year cadence and C++11 contains the largest single language change. Explains the 1998 implementation delay, the concepts yo-yo that delayed features, and claims future releases cannot match C++11’s impact, so adoption patterns and toolchains now split teams by feature set.
AI-written summary · about
chapters (4)
related talks
55mNot your GrandParent’s C++
48mEarly Modern C++: How to Handle a C++03 Codebase in $CURRENT_YEAR
47mLearning (and teaching) modern C++ - Challenges and Resources
01h 01mLearning (and teaching) modern C++ - Challenges and Resources
01h 25mComparing 'Classic C++' and 'Modern C++' Ways to Solve Programming Tasks
44mC++ – The Newest Old Language
01h 06mModern C and What We Can Learn From It
01h 37mC++ And Beyond: Discussion