Buffer overflows were last seen on the OWASP top 10 list in 2004. Favoring of anything else over C for most things is a pretty obvious reason why. A language change destroyed an entire class of bugs.

because no compiler can check to see if you thought of everything.

We can try to get closer to that with better language design. You'll never get there but I think there are obvious benefits as to why you'd want to do that.

I write way less bugs in Rust than I have in Java or C++, and that's mostly thanks to the language design.

I'm just tired of people entirely dismissing languages like C because they don't have these features. Especially when the operating systems their code runs on and their languages may even be implemented in C!

Because that code has been review and re-reviewed and patched by experts in the field for years. You're not gonna write a backend for an app with short deadlines in C because that would be absolutely fucking insane.

It's a "tool for the job" game. I don't trust a junior developer to write a login system. I've found security flaws in login systems written by senior developers who "know what they're doing TM". Unless I'm the expert in a given domain, it's better to trust something written by those experts.

For the record (since it's fixed anyway), I discovered a common login timing vulnerability on one of our production systems that had been in place for nearly 15 years. Luckily we didn't have enough traffic for anyone to notice it before me.