C++ needs to be more secure, but it need not be replaced
Briefly

Bjarne Stroustrup, the inventor of C++, has urged the programming community to defend the language against criticism regarding its memory safety issues. Cybersecurity experts have raised concerns about manual memory management in C++, causing potential security vulnerabilities. Despite proposed initiatives like TrapC and Safe C++, Stroustrup warns that the rise of languages designed for memory safety, like Rust, could threaten C++'s future. He asserts the necessity for enhanced security measures while rejecting a complete transition to new languages, advocating instead for C++'s continued evolution and improvement over radical changes.
C++ has always had a strong focus on security. According to him, these principles remain essential to the future of the language.
Stroustrup sees this as a major threat to the future of C++. He points to earlier statements by Microsoft, in which the company suggested that C/C++ should be replaced by Rust for new projects.
The U.S. government agency CISA also recently announced that manufacturers must have a strategy to ensure memory safety by 2026.
Pressure on C++ is coming from several quarters. [...] Google has also recently indicated its intention to focus more on memory security than on modernizing C/C++.
Read at Techzine Global
[
|
]