Discussed recently:<p>Feds: Critical Software Must Drop C/C++ by 2026 or Face Risk (01.11.2024)<p><a href="https://news.ycombinator.com/item?id=42013379">https://news.ycombinator.com/item?id=42013379</a>
If the USG wants this then they need to start inserting it into Statements of Work then companies bidding on this type of work can assess impacts and provide a business case. It will be slow but start there. The same way Risk Management Framework works, DoD 8570, etc
Linus does not use standard C either. Linux kernel depends on -fwrapv switch (reduced UB on signed ints). Also in discussion about Rust mentioned the kernel has lots of infrastructure that almost makes C into different language.
Rust should just build their own super safe OS, instead of nagging existing projects to adopt their practices. If they can successfully build an another successful OS it is much more convincing.
1991 Edition<p><a href="https://www.gao.gov/products/imtec-91-70br" rel="nofollow">https://www.gao.gov/products/imtec-91-70br</a><p><pre><code> Pursuant to a congressional request, GAO obtained information on the Department of Defense's (DOD) implementation of legislation which mandated using the Ada programming language for all software development, where cost-effective.</code></pre>
> If only it were that easy to snap your fingers and magically transform your code base from C to Rust. Spoiler alert: It's not.<p>This misses the point. The point is to start moving in that direction, not instantaneously.
What's really needed is an official Engineering qualification for programmers, like you leaglly have to have if you're an Electrician or Gas Engineer, etc. Liability Insurance in case of damaging bugs.<p>Literally anyone can call themselves a Software Engineer, which one the one hand is great because it's accessible, but also a curse in terms of making it a respected profession.