Assuming that C is the most successful language of its generation, among those letting purposely do anything with memory access, well, it's unfortunately possible to have it do anything. It's like saying with surprise that a harpoon gun may even kill people.

Then successively implemented languages may have improved things (or they would have been useless efforts). When a single one of them will reach half the popularity of C (without running in any "unsafe" mode) it will be another great success.

The original article was clearly just a polemical overkill by a maniac of another language. Or by a fisherman who kills fishes slapping them.

With the exception of the C++ case, these all seem to result in DDOS which, while bad, are barely security issues. It speaks to the difference between C and these other languages (Go, Python, Rust).

A crash is always better than OOB memory reads. All of these are crashes except the C++ one. The rust one is from 3 years ago and listed twice.

This article is about the frequency of these bugs, not their existence. C and C++ are the only languages where this happens regularly

It's a pun on The Onion's repeating headline about gun deaths in the US ("only country where...") [1] . I thought it was pretty clear before I clicked it it was going to be talking about security vulnerabilities in C, but I live close to that world so I might be a biased audience.

[1] https://en.wikipedia.org/wiki/%27No_Way_to_Prevent_This,%27_...

My guess is its almost exclusively due to the reference its making to the similarly titled Onion article. The actual article linked is basically a cut and paste replacing gun violence with memory vulnerabilities.

Clicking on the link does not help either save the rightful first impression.

Because it is shitposting maybe (that's why I flagged it). Shitposting (esp the lowest quality kind) does not seem to be leading to interesting discussions.

The critique is more that the average, or at least loud, C programmer is resistant to fixing these problems (for example via Rust) and often arrogantly claim it's just a skill issue.