Everyone I seem to talk to hates Apache for performance and swears up and down for something else. So why hasn't something else topped Apache in popularity?
Exactly this.Also it's pretty easy for something to stay popular. It's free, pretty simple to configure, ubiquitous, common on shared hosts, supports most people's needs out of the box..
Perhaps you can help me?I'm an nginx guy myself, far easier to configure than apache when working from scratch (not to mention more powerful, with basic logic built into the configuration files and even perl, lua, etc. as options)
exactly apache is more set and forget.. not to mention alot of linux distributions include apache by default - sure that helps tooExactly this.
It's not a matter of flipping a switch to migrate servers, domains, etc. from Apache to something else... when you have to reconfigure every server, every website on that server, every rewrite rule for every website, etc. it's not a simple task. I use Nginx on my dev servers, but my production servers are still Apache simply because it's a massive undertaking just to convert my own websites.
One can ask the exact same question about operating systems and why Windows is still popular... it's popular because it's easy to *stay* popular and supports most people's needs out of the box.
exactly apache is more set and forget.. not to mention alot of linux distributions include apache by default - sure that helps too
nginx need's tender loving care more often due to lack of htaccess and mod_rewrite support and need to convert to nginx rewrites
If you tally up all system admin related hours used to setup, configure and maintain apache or nginx over a course of 12 months, you'll find nginx consumes way more of your time than apache. More sites in the mix, the higher that nginx system admin/maintenance time gets
I'd say nginx will overtake apache when native .htaccess and mod_rewrite support are added - I hear nginx 2.x has plans for that ?
Yeah depends, for a web host it would be considerably more i.e. add a new shared hosting account where one client has magento script, another new account with client needing wordpress or a few with different plugins that depend on htaccess i.e. W3TC or super cache, another with xenforo, another with IPB or vb etc etc.. Add the possibility that each client has different custom permalink setups etcI haven't seen Nginx being more hours to admin vs Apache once the site(s) are setup... In fact it seems to be less. For example Adding SSL support and SPDY support is less work with Nginx I found. I definitely think migrating from Apache to Nginx would be more widespread if it had a true way to just handle Apache .htaccess and rewrite rules 100% without needing to change anything. I suspect that's the biggest annoyance for people.