Google's take on memory safety

[Paulo Pinto]

On Friday, 8 March 2024 at 09:09:12 UTC, Monkyyy wrote:
> On Friday, 8 March 2024 at 04:50:38 UTC, Walter Bright wrote:
>> On 3/6/2024 9:16 AM, H. S. Teoh wrote:
>>> Called it.
>>
>> I announced at the Berlin DConf that C was doomed because of 
>> memory unsafety!
>
> C is still here, C will continue to be here until something 
> else drastically makes it worth while to redo the gaint stack 
> of code that is gnu and the linux kernal which dispite many 
> many delusional proclamations, errrr no I'm not swapping to a 
> rust os anytime in the near future.
>
> *Why are you proud of a wrong prediction*, being remade by loud 
> corps who will also be wrong.
>
> https://www.tiobe.com/tiobe-index/
>
> Python and java, and js are not exactly safe languges, there no 
> way to inturpt the high ranking as being coherently designed 
> around safety.
>
> Headlines and noise that poeple reshare to feel smart but do 
> not change thier behavior, are not reality.

"The US government says it would be better for them if you ceased 
using C or C++ when programming tools. In a recent report, the 
White House Office of the National Cyber Director (ONCD) has 
urged developers to utilize “memory-safe programming languages,” 
a classification that does not include widely used languages. The 
recommendation is a step toward “securing the building blocks of 
cyberspace” and is a component of US President Biden’s 
cybersecurity plan."

https://readwrite.com/the-nsa-list-of-memory-safe-programming-languages-has-been-updated/

The issue at hand in safety from memory corruption, not 100% 
safety.

Just wait until delivering software written in C or C++ requires 
a biohazard symbol "handle with care" kind of regulation, and 
insurance companies high premiums on software developed with such 
languages.