[j-kidd]

Apache, while not hipster-compatible, is still very much alive.

> I think it may be time Apache itself branches out to a leaner version (with the kitchen sink build available separately) that's as bare-bones as possible with basic functionality that can still be easily extended by modules later.

Right. Here's a binary size comparison between Apache 2.4.6 and Nginx 1.4.1:

    ~ $ ls -l /usr/sbin/apache2
    -rwxr-xr-x 1 root root 580528 Jul 26 13:23 /usr/sbin/apache2

    ~ $ ls -l /usr/sbin/nginx 
    -rwxr-xr-x 1 root root 661264 May 24 07:42 /usr/sbin/nginx

Apache is totally modular. Going from Apache to Nginx would be a downgrade for me.

[eksith]

When I was referring to "leaner", I was referring to the apparent ease with which Nginx serves while Apache was having difficulty in the same setup (it's quite silly to compare binary sizes). I'm not sure if that makes it not "hipster-compatible" any more than not as performance compatible while running on the same iron and facing the same load.

Also of note, as teilo mentions (https://news.ycombinator.com/item?id=6151215), sometimes you want to decouple the app/scripting engine from the web server.

FYI, current stack is OpenBSD, Nginx, PHP-FPM and Postgres. Does that make us hipsters?