I work on software supply chain security at MITRE, including serving as amember of the OmniBOR Working Group, where I lead development of the Rustimplementation, and as the project manager for Hipcheck, a tool forautomated supply chain risk assessment of software packages.

Lobsters is a community-driven platform for sharing and discussing links to articles, tutorials, and projects related to technology and programming. Readers can learn about a wide range of topics, from software development and system administration to cybersecurity and artificial intelligence. With user submissions, comments, and voting, Lobsters provides a platform for collaborative learning and knowledge sharing among technology enthusiasts.

Lobsters

C++ must become safer due to the critical societal impacts of software vulnerabilities, particularly those related to memory safety. While rewrites to Rust offer memory safety benefits, they are not always feasible or cost-effective for existing C++ codebases. The C++ community is exploring multiple paths to enhance safety, including contracts, profiles, successor languages, and borrow checking. These efforts are essential as C++ continues to play an important role in many critical systems, and the community must work towards making it safer.

C++ Must Become Safer — Andrew Lilley Brinker — Software Supply Chain Security

We Should All Care About C++ Becoming Safer

<p>The reports state that experts on the field were consulted … As far as Stroustrup knows nobody from the C++ committee were consulted. Pretty one sided statement, from the policy makers as usual.</p>


<p>Just accept that rust is better than cpp and go with it</p>
