News for hackers. Stuff that matters.
Re:The Architecture of Open Source Applications: Nginx by DantesRequiem on Monday November 23, 2015 @05:28PM (#10617806)
Historical reasons...after nginx started blowing Apache's performance out of the water, Apache addressed some fundamental architectural issues and caught (mostly) up.

As an example, I would refer you to a discussion down this thread about Apache 1.x forking for concurrent connections.

Re:The Architecture of Open Source Applications: Nginx by ryuuchin on Monday November 23, 2015 @06:10PM (#10618025)
Also just for context remember that on linux forking and threads are basically the same thing so you can't just switch out one for the other and expect performance to change (it won't).
Re:The Architecture of Open Source Applications: Nginx by WildUtah on Monday November 23, 2015 @08:14PM (#10618536)
"forking and threads are basically the same thing"

It's nowhere near that simple. You can fork lightweight like threads or heavy. One of the terrible things about Apache performance was all the heavy forking on every single request for generated pages. That was back when it was really expensive.