C++, like all things, has numerous problems. Pointing out how Rust addresses many of them is a major topic of my blog, but some of the problems are bigger than others. The biggest, most famous, loudest problem, the problem that got the federal government’s attention and resulted in a surreal flame war between Dr. Bjarne Stroustrup and the NSA (which I also commented on/contributed to), is C++’s lack of memory safety.

The Coded Message's resource offers insights, tutorials, and resources for software developers and technology enthusiasts. Readers can learn about coding best practices, software architecture patterns, and emerging technologies. With articles, tutorials, and code samples, The Coded Message provides  guidance and expertise for building software applications and advancing technical skills.

The Coded Message

C++'s lack of memory safety, highlighted by issues discussed between Dr. Bjarne Stroustrup and the NSA, remains its biggest problem. While migrating to memory-safe languages like Rust, Java, or C# is a solution, there is also a possibility of making C++ itself memory safe through initiatives like Circle C++. The post argues that memory safety will become a standard expectation across all programming languages, pushing C++ towards legacy status.

Can C++ fix its biggest problem?

Can we migrate C++ programmers to a safe programming language? #

Can C++ itself be made suitably memory safe? #

<p>Its not unsafe if you know how to use it.
But i think the article aligns with current day and age. Everything needs to be safe with big warning labels.</p>
