The C++ standard is a dense document. Thousands of pages of normative text, cross-references, and carefully worded requirements that govern how every conforming implementation must behave. Most developers read the current version in isolation when they consult it at all. What gets lost is the history: how a section looked in C++11 versus C++17, what wording changed between C++20 and C++23, and why.
Jason Turner built something that makes that history visible. The C++ Standard Evolution Viewer presents the standard as a series of side-by-side diffs, letting you compare how sections evolved across language versions. It concentrates on what Turner calls Tier 1 sections, the major library components and language features that offer the most educational value. That includes sections like [array], [class.copy], and [ranges.adaptors].
The value here is not purely academic. When you are debugging a subtle behavioral difference between compilers targeting different standards, or trying to understand why a library interface changed, reading a diff is often faster than reading two full sections and mentally comparing them. The committee makes changes for reasons, and those reasons are frequently legible in the delta.
[ranges.adaptors] is a useful example. The ranges library shipped in C++20 and was refined in C++23. Seeing what changed between those two versions in the actual normative text, rather than in a change summary or a third-party blog post, produces a different kind of understanding. You see exactly what was added, what was removed, and what was reworded.
[class.copy] is another worthwhile section to trace. Copy and move semantics have been part of C++ since C++11, but the wording around them has been tightened and clarified through several subsequent versions. A diff view surfaces those incremental clarifications in a way that reading each version in sequence does not easily reproduce.
This kind of tooling is sparse for programming languages in general. Version control gives us diffs for code, but language specifications tend to be treated as static artifacts, published and then superseded. Turner’s viewer applies the same mental model to the standard itself. For anyone who reads the standard regularly, or who wants to build that habit, the interactive diff format makes the document more approachable and the focus on high-value sections keeps the experience from becoming overwhelming.