Hacker News new | past | comments | ask | show | jobs | submit
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.

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.

loading story #50572421
The problem are the technologies written in them, that we aren't replacing any time sooner.

I work mostly in compiled managed languages, yet have to keep my C and C++ skills sharp, as there is always this or other scenario that requires something written in them, like the runtimes or compiler tools I depend on, because bootstraping is too much work for most implementors.

loading story #50566195