Let’s Stop Bashing C
I could care less about integer division and minor details of syntax, but that&#x27;s not going to stop me from being grumpy about C&#x27;s continuing popularity.<p>Every C program I have ever worked on has been riddled with integer overflows, undefined behavior, buffer overflows and bugs. This was perfectly acceptable for a Vax or a Sun workstation in the 80s, and at forgivable in the mid 90s when plenty of developers still only had 8 MB of RAM and wasted half of that on Netscape Navigator.<p>But we live in an age of Pwn2Own and ClusterFuzz, where even the tiniest of bugs can be used as step 4 in a 6-step exploit, and where C compilers reserve the right to completely and silently break your program at the faintest whiff of undefined behavior.<p>I know my limitations: I&#x27;m not smart enough to write C code that deals with hostile data off the network. Neither are the authors of 99% of the C code that I&#x27;ve seen, with the possible exceptions of djb and a few OpenBSD contributors. It&#x27;s long past time to invent and use better systems languages. Choose what you want, but choose something safer.