upvote
The good news is that this was already the case, and we have tools that check for this; like fuzzers and sanitizers.

Now to get people to use them it's an issue.

reply
We have had fuzzers and sanitizers for decades. Despite their widespread use, we still experience a deluge of memory safety issues in memory unsafe languages, including in projects that heavily lean on these tools.

The actual good news is that we have multiple mature languages that entirely remove the need for users to configure and run fuzzers and sanitizers and remember to always obey arcane rules in order to avoid memory corruption.

We’ve been encouraging people to walk, not run, to the exits and switch from C and C++ to memory-safe equivalents. Now it is clear that the time for walking is over and the remaining holdouts should be at the very least jogging if not running.

reply
Ah yes, the "programmers just need to be better" argument.

I would prefer something be impossible by construction.

There are memory-safe options with little/no performance overhead compared to C/C++.

reply
This is bad news for computer industry. See the recent Java4Shell.
reply
because the assembly for the base64 decoding was handwritten, the paren't comment is still valid
reply
I think the point is that the weakest link WILL be found.
reply
Good news for the computer industry employees though.
reply
At least C folks can use something like BoehmGC and calm down things a little.
reply