Revitalizing C++: Balancing Safety, Efficiency

Revitalizing C++: Balancing Safety, Efficiency, and Legacy

C++, a language renowned for its raw speed and flexibility, stands at a pivotal juncture. As software engineering increasingly prioritizes safety, C++ finds itself in a contest of evolution with languages like Rust, which champion safety by design. At the recent CppCon 2025, John Lakos, a senior architect at Bloomberg and an influential figure in the C++ Standards Committee, delivered a compelling talk on this very subject.

The Evolutionary Imperative

Lakos' presentation, titled "Making C++ Safe, Healthy, and Efficient," underscores the urgency for C++ to adapt. "C++ has come under criticism," Lakos notes, highlighting the growing scrutiny from regulatory agencies and the cybersecurity community. As these entities question the safety of legacy systems, the pressure mounts on C++ to innovate without sacrificing its hallmark efficiency.

The central thesis of Lakos' talk is that C++ must embrace a safety-first paradigm while maintaining its performance edge. This involves adopting safety mechanisms and safety-by-default principles to better support the developer ecosystem. "We want safety, but not at the expense of needed performance," Lakos insists, reflecting the delicate balance the language must strike.

Safety, Correctness, and Efficiency

In defining safety, Lakos broadens the scope to include correctness and security. "Correctness matters. Security matters," he asserts, emphasizing that a program is not safe if it is vulnerable to exploitation or fails to perform as intended. This expanded definition demands an ecosystem that supports robust development practices and discourages potential migrations to other languages.

However, Lakos distinguishes between runtime efficiency and runtime checking, cautioning against the misconception that these are inherently at odds. "There isn’t a contradiction between runtime efficiency and safety," he explains, though acknowledging the challenges posed by runtime checking.

The Role of the C++ Community

The evolution of C++ is not a solitary endeavor. Lakos calls for a collaborative effort within the C++ community and industry stakeholders. "We all should pitch in like NATO and get it done," he urges, drawing an analogy to collective security. The roadmap for C++26 and beyond is not merely a technical blueprint but a collective mission to secure the language's future.

Lakos also sheds light on the often opaque process of standardization, humorously describing it as "how the sausage is made." The journey from proposal to standard involves extensive prototyping and collaboration, with Bloomberg playing a pivotal role in sponsoring open-source initiatives and prototyping new features.

Addressing the Competition

The talk does not shy away from the competition posed by Rust, a language that has gained traction for its emphasis on memory safety and concurrency. Lakos acknowledges Rust’s appeal but questions the necessity of abandoning C++. "If all of you knew right now that C++ 32 would be just as safe as Rust, would you really be so excited to run away?" he challenges.

This rhetorical stance is underpinned by a pragmatic recognition of the immense software capital invested in C++. Lakos argues for incremental improvement, preserving existing investments while positioning C++ as a viable choice for modern development challenges.

A Path Forward

The path forward for C++ involves not only technical enhancements but also cultural shifts within the developer community. Lakos envisions a future where C++ is easier to use securely and correctly, closing the gap with languages perceived as safer. This vision requires sustained investment in ecosystem support, from tooling improvements to educational efforts.

In conclusion, John Lakos' talk at CppCon 2025 is a clarion call for the C++ community to embrace change. It is a roadmap for revitalizing a language that, while mature, is far from obsolete. As the software landscape evolves, so too must C++, balancing its legacy of performance with the imperative of safety.

By Samira Okonkwo-Barnes, Buzzrag Tech Policy & Regulation Correspondent