3 ms·

Agreed. I'd throw nginx into that cohort as well.

• sneak 9y ago
  Someone recently suggested that I read the nginx source code, as it was some of the most comprehensible and clear C he'd ever seen. I can definitely cosign that, having now done so. It's amazing!
  • meredydd 9y ago
    Hey, can I ask you what prompted you to just go reading nginx code? As pointed out recently, most people - even people who advocate reading source code for its own sake - don't actually read code unless they have to. (http://akkartik.name/post/comprehension http://akkartik.name/post/comprehension) So it's interesting to see a counterexample. What led you to go spelunking in nginx?
    • stevekemp 9y ago
      (Not parent.) I used to read source-code specifically to look for security problems. Auditing of code as a small hobby. I found some fun issues over the years. Reading code has become a habit these days. If I depend upon a library I try to glance at it. If I install a new application I try to have a read of some of it. It stops you from blindly depending on poor-quality software, and sometimes makes you choose an alternative.
    • sneak 9y ago
      An associate was writing lua nginx stuff and needed to refer to the c to find some event names or something. He noticed how nice it was and told me to take a look because the quality impressed him so much, so I read it for fun. Also, I have seen so many problems arise from the fact that code is easier to write than to read, so I consciously make an effort to not avoid reading code, and I’m sure that leaked over here.