The Evolution and Standardization of C++: From C++98 to C++20

The transcript details the arduous yet essential process of standardizing the C++ programming language under ISO rules, initiated in the late 1980s. Bjarne Stroustrup recounts how industry giants like IBM and HP pushed for formal standardization to ensure C++'s independence from any single corporate owner and to foster its widespread adoption. The process, described as an open, consensus-driven, and international effort, involves regular meetings, technical discussions, and voting by representatives from various organizations across numerous countries. This standardization ensures C++ remains a robust, portable, and universally accepted language, crucial for the global systems that depend on it. Stroustrup highlights the distinction between the initial, longer standardization cycles (like the 8 years for C++98 and 13 years for C++11) and the current, more agile three-year release cycle. He explains the "second system effect" where increased ambition after initial success led to delays, and the "bright idea" syndrome where significant features were proposed late in the cycle. The shift to a predictable, shorter release schedule for C++14, C++17, and C++20 was a deliberate strategy to combat these issues, ensuring timely delivery and better support for implementers. The consensus-based voting system, where a 60/40 split is avoided to prevent dialects, underscores the commitment to a unified language. A key practical insight is the importance of predictable release cycles for complex technical standards. The move from a decade-long cycle to a three-year one significantly improved the ability of compiler and library implementers to target and deliver features on time, fostering a healthier ecosystem. The open, democratic, albeit "horrifying," nature of the standardization process, where individuals from various organizations contribute and vote, is presented as superior to a single entity dictating the language's evolution. This distributed governance model ensures broader acceptance and resilience. The standardization of C++ serves as a microcosm for the broader challenges and successes in managing complex, globally adopted technologies. It illustrates the tension between innovation and stability, the necessity of collective governance for critical infrastructure, and the human element of ambition and bureaucracy in technical development. The analogy to democracy, though imperfect, emphasizes the value of a messy, open process over autocratic control, ultimately leading to a more robust and widely supported outcome that underpins countless systems worldwide.

we are standardizing C++ under iso rules which are very open process people come in there's no requirements for education or experience

our organizations depend on C++ we cannot depend on something that's owned by another corporation that might be a competitor

you really want to be part of it because basically otherwise we'll do it ourselves and we know you can do it better

it's a bunch of people in a room deciding the design of a language based on which a lot of the world's systems run

the standardization is not pleasant it's it's it's horrifying like democracy what we exactly as Churchill says democracy is the worst way except for or the others right

we work on the basis of consensus that is we do not want something that passes 6040 because then we're going to get dialects and opponents

this was sort of like a second system effect that is we now knew how to do it and so we're going to do it much better and we've got more ambitious ambition and it took longer

we decided ever again and so how do you avoid those slips and the answer is that you shipped more often

the STL stuff that that I basically I think it saved C++ it was beautiful

delivery on time is good