On 5/3/2026 2:45 AM, Lawrence D’Oliveiro wrote:You have mentioned that thing many times.On Sun, 3 May 2026 11:25:00 +1000, Subcommandante XDelta wrote:There was memory safe C 40 years ago. No one was interested.With $1 Cyberattacks on the Rise, Durable Defenses Pay Off Writing>
memory-safe code beats patching your way to safety
Rust seems to be the language du jour for tackling this problem.
>
Google reported a significant decrease in memory-related bugs after
adopting Rust into the Android code base in a major way. Though,
oddly, not a decrease in bugs overall ...
But it is a rather incomplete story.
Was it a C with array bound checking or was it a
memory safe C? Memory safety is more than array
bound checking.
Was it a good compiler? A good concept with a bad
implementation will not succeed. Compiler bugs and/or
poor optimization can kill the best compiler ideas.
Did it have the commercial support needed to succeed
in the market? Even technical good products need to
be advertised to the right audience at the right price.
We know it did not fail because developers do not want
memory safety. Memory safe languages are used in the vast
majority of code written today (Python, JavaScript, Java,
C# and PHP usage far outnumber C and C++ usage today).
Arne
Les messages affichés proviennent d'usenet.