He provided recommendations to fix the mistakes instead of just dissing the whole thing. If you want people to write better code, share what you know.
Makes me wish Zed had a "Learn C the Hard Way" to complement what he's doing with Python.
I sure would like a 'hard way' courseware for C. (in addition to my trusty copy of K&R C for reference)
Thank you for calling attention to the second comment.
C is serious business.
(Incidentally, I've written event-driven programs with libev in both C and Perl. My load is usually so low that doing it all in Perl does not affect the number of requests I can handle, nor does it impact latency. The IO is the bottleneck; the article even says it only uses 2% CPU. Why risk insecurity when you don't know C and it doesn't even improve throughput?)
How can we take posts like this seriously?