Is C++ Heading for Obsolescence? Inside the Language’s Growing Divide

C++’s future has become a contentious battlefield, with heated arguments on Reddit and serious discussions within the ISO C++ standards committee. The Evolution Working Group (EWG) recently adopted P3466 R0, reaffirming design principles that reject ABI‑breaking changes, prohibit “viral annotations,” and emphasize zero‑overhead and backward compatibility.

External Pressures

U.S. agencies such as CISA, NSA, and the White House have issued warnings urging the tech industry to avoid memory‑unsafe languages, effectively discouraging C++. Major tech companies are also moving toward Rust: former Microsoft C++ chair Herb Sutter left for Citadel Securities, Microsoft’s Azure CTO advocated abandoning C/C++ for new projects, and Google has been pushing Rust for Android to reduce memory‑safety bugs.

Google’s Rust effort is illustrated by the open‑source tool https://github.com/google/crubit, which enables C++/Rust interoperation. AWS similarly promotes Rust for performance‑critical services such as S3, CloudFront, EC2, and Lambda.

Community Fracture

Within the C++ community, two opposing factions have emerged:

Modern, well‑funded tech firms that view their codebases as valuable assets and invest in automated refactoring tools (e.g., Google’s Clang‑based large‑scale refactoring of over 100 million lines of code).

Legacy‑oriented enterprises that cling to old practices, fighting over minor code‑style issues and lacking resources for large‑scale modernization.

Both sides agree that tooling is the decisive factor; the language itself is less disputed than the ability to manage versioned source code cleanly.

Technical Challenges and Proposals

Herb Sutter stresses that any change must avoid forcing existing codebases to modify even 1 % of their lines unless mandated by regulation. The committee’s focus on ABI stability and zero‑cost abstractions often conflicts with the desire for modern features like modules and safe configuration files.

Proposals such as “Safe C++” and full‑lifecycle annotations have struggled to gain traction because the committee prioritizes backward compatibility over radical redesign.

Outlook

Without a unified build system, package manager, or robust tooling, C++ risks further fragmentation. In contrast, languages like Go demonstrate how strong tooling can drive adoption. The article concludes that unless the C++ ecosystem embraces modern tooling and accepts the cost of migration, the divide between modern and legacy C++ will likely deepen.