Expose a C program with all the language's subtle undefined states and manual memory management to the big bad web! What could go wrong...
Everyone here is completely glossing over this as if it were suggested that this is intended for everybody, for every solution. If you're not extremely confident in your C skills, or have the experience to back it up, This is NOT for you! If you think you can only do it with another language, then This is NOT for you! If you think you're gonna write the next Amazon, This is NOT for you!
And lets not forgot just how many things are written in C and still running the internet. It's just another tool in your toolbox.
That’s not to say that other languages are perfect, but there are much safer options that are still very fast, such as Rust, or even C# or Java.
Sick of the C Apologism Task Force's idea that "if only rockstar programmers wrote code we wouldn't have any problems", completely ignoring the reality of software development and the evidence of 50 years of exploits.
As for Linus, the kernel was written when he was a student, and I doubt he personally still makes the same low hanging fruit vulnerabilities that are the big issue.
I hate to break this to you, but that describes almost every TCP/IP stack and network adapter driver in deployment.
(Not to mention httpd servers, and programming language interpreters written in C.)