Yes, it's fairly stable (I'm still having some issues on one site with Debian - my other site I had to go back to nginx for stability).
One thing I didn't like was that the DDOS protection (limitation of number of connections from 1 IP) didn't work in it. It's not that big of a deal since I do that via iptables, but it is an issue.
yeah, yeah.. I keep hearing that or "it's under consideration"...
Would make it nicer, since I hate setting up a base nginx on Debian since you have to pretty much customize it all yourself. I've got a template I use now though, so it's not so bad.
Nginx abandoned that because it's wildly inefficient with resources.
If you have htaccess on, you need to parse the current directory, plus all directories above it searching for .htaccess files for every single request, which becomes a HUGE amount of workload, which is one of the reasons apache is slow. This is apache loading the config files over, and over, and over again, which requires text parsing each time.
Nginx takes the configuration in it's config files, and loads them at startup, in an essentially compiled form.
Apache 2.4 actually defaults to htaccess being disabled, just like nginx.
It actually is possible to make nginx do what you want it's more complicated to setup.
I actually did a software engineering school project on that topic.
Setup a main nginx process on port 80
Setup additional nginx processes in systemd containers.
Let the user enter the domain name they want to use via web interface
Proxy the domain to the correct backend nginx process.
Give them control of their individual nginx process
htaccess is just a bad design
If you have multiple IP addresses, you also could just run one nginx process per IP address, and just give each person their own IP