Original link: Feds: Critical Software Must Drop C/C++ by 2026 or Face Risk / TheNewStack.
They have said it before, but they are now saying it again. And even more clear.
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
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
Not anything ambigious or subtle in that!