I disagree. Nginx brings a lot to the table in simplicity and ease-of-use.
Just reading an nginx.conf and comparing it to an httpd.conf should be enough to convince you what nginx brings to the table.
Just reading an nginx.conf and comparing it to an httpd.conf should be enough to convince you what nginx brings to the table.
On the high end, provisioning is fully automated.
Not to mention the fact that after > 15 years(!), amateur sysadmins like me can pretty much dream the config settings.
Which leaves a relatively small target audience for whom a simpler config is even remotely relevant.
And why should these five lines be buried in a 5000 line conf file?
The average user only ever has to access one small file with 10-15 lines.
The mandatory configuration is actually pretty minimal, especially if you are using it as an app server. Take, for example, http://kasparov.skife.org/blog/src/wombat/httpd-conf-cool.ht... which sets up a bunch of mod_wombat (precurser to now-bundled mod_lua) stuff.