"No way to prevent this" say users of only language where this regularly happens

For anyone who doesn&#x27;t regularly follow The Onion, the verbiage in this post is directly copied from the story The Onion posts after every major mass-shooting in the United States.<p>An example: <a href="https:&#x2F;&#x2F;www.theonion.com&#x2F;no-way-to-prevent-this-says-only-nation-where-this-r-1848971668" rel="nofollow">https:&#x2F;&#x2F;www.theonion.com&#x2F;no-way-to-prevent-this-says-only-na...</a>

Very funny!<p>I just did some coding on C for the first time in years. Now, ok, i&#x27;m out of practice, but I&#x27;m generally a fairly cautious programmer. I got so many seg faults and weird memory errors in my code. Valgrind found some more that I hadn&#x27;t spotted.<p>It&#x27;s just too easy to screw it up. Much better to use languages that remove entire classes of bug without you having to even think about it.

Related (as linked in the article):<p><i>CVE-2023-6246: Heap-based buffer overflow in the glibc&#x27;s syslog()</i><p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=39194093">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=39194093</a>

I&#x27;m almost positive the project being dunked on here is older than the author. There are plenty of reasons to hate glibc, but nothing productive comes of this kind of noise. It&#x27;s not like heap overflows are impossible in other languages. Consult <a href="https:&#x2F;&#x2F;github.com&#x2F;rust-lang&#x2F;rust&#x2F;issues&#x2F;80894">https:&#x2F;&#x2F;github.com&#x2F;rust-lang&#x2F;rust&#x2F;issues&#x2F;80894</a> or consult your preferred CVE database.<p>Would love to know what language the author thinks glibc should have been written in in the late eighties.

&gt; users of the only programming language in the world where these vulnerabilities regularly happen once or twice per quarter for the last eight years<p>I wish!

Rewrite in Rust?