Post

In a CRA webinar last week, I commented it is possible that C/C++ are a per se CRA violation, since C/C++ are insecure by design. An attendee replied "but C/C++ is what embedded use" and I said, more or less, "tough". Here's @gregkh.bsky.social on it: www.zdnet.com/article/rust...

To put it another way: if the official position of the Android and Linux kernel teams is “we, some of the world’s best coders, can’t safely use C” then the bar under CRA’s requirements of “safe by design” should be nearly impossible to meet for mere mortals when using C.

Not saying people should use C, but if we were to extend that to what ~every application is deployed on, not to mention faultlore.com/blah/c-isnt-... … that implies it's impossible to meet for anyone.

impossible to meet for anyone _today_ , sure but at the very least we should have governments procurement rules block the spending of taxpayer money on negligent technology choices after some future date e.g. 2050 ? 2060 ? just needs a line in the sand for incentives

Definitely. But that's a different bar than "CRA this September".