"The development of new product lines for use in service of critical infrastructure or [national critical functions] NCFs in a memory-unsafe language (e.g., C or C++) where there are readily available alternative memory-safe languages that could be used is dangerous and significantly elevates risk to national security, national economic security, and national public health and safety," the report says.
"Putting all new code aside, fortunately, neither this document nor the U.S. government is calling for an immediate migration from C/C++ to Rust — as but one example," he said. "CISA's Secure by Design document recognizes that software maintainers simply cannot migrate their code bases en masse like that."
But for all new code, bros it's ogre.
"For existing products that are written in memory-unsafe languages, not having a published memory safety roadmap by Jan. 1, 2026, is dangerous and significantly elevates risk to national security, national economic security, and national public health and safety," the report said.
It's ogre.
Jump in the discussion.
No email address required.
C++ was doomed as soon as industry growth outpaced the supply of programmers capable of comprehending the concept of memory at all.
Anyways I don't consider this a bad thing I consider it job security
Jump in the discussion.
No email address required.
how bad is the rise of jeetcode, is it on par with other clueless programmers or is it far worse
Jump in the discussion.
No email address required.
More options
Context
Jump in the discussion.
No email address required.
I mostly just write C but C++ comes out when I dont feel like rolling my own functions
Jump in the discussion.
No email address required.
More options
Context
More options
Context
You need to understand how memory works to write good Rust code at least as well as you need it to write good C++ code.
Jump in the discussion.
No email address required.
More options
Context
More options
Context