[CalRobert]

I started needing to configure web stuff about 6 or 7 years ago. At the time, I could use nginx or Apache. I spent a bit of time (maybe 20 minutes) with Apache since I'd heard of it, thought "Ugh this is a pain and I just want to move on to the fun parts of this project and not banal config details", and then tried nginx. It was much easier, and I've never bothered to learn Apache. To be honest I've kind of assumed it wasn't worth learning since it seems to be in slow, but persistent, decline, and I've never needed to learn it for a particular project.

I wonder if anyone else had a similar experience. If the first 20 minutes are nicer with one tool over the other, I suspect most people will stick with that tool until it starts limiting them.

I don't think any of the stuff you mention is related to that.

[GlennS]

I've had the experience in the reverse order, but with the same conclusion.

First lot of web server configuration I had to do was Tomcat. After that, IIS 6 through to 8.

Compared to any of those those, writing Apache httpd config actually seems pretty straightforward.

But yeah, Nginx is a lot plainer and I pick it most of the time. Usual time when I don't is if deploying someone else's software with complicated rules and don't have the time to port them.

Damn Tomcat config is godawful gibberish. Seems to be a running theme in Javaland.

[merpnderp]

This was exactly my experience. I learned Apache and knew how to configure it. But once I tried Nginx I never wanted to fuss with an Apache config again.