True, and False.
You're projecting your own experience.
I have a pretty good idea what decent C looks like, as does anyone else who spent 30 years using it.
You're projecting your own experience.
I have a pretty good idea what decent C looks like, as does anyone else who spent 30 years using it.
Source, the Linux Kernel Summit 2018 and the Google sessions on kernel security.
According to Google 68% of 2018 CVE's were caused by C's lack of bounds checking.
Google is also collaborating with ARM on their memory tagging extensions to tame C.
Like everyone else you can go watch the Linux Kernel Summit 2018 talks.
Oracle also thinks otherwise, hence Solaris with SPARC ADI memory tagging turned on by default.
DoD has a report where UNIX typical exploits weren't possible in Multics thanks to PL/I instead of C.