Apache2 is still better for servers that host lots of small applications (largely due to htaccess enabling "per directory" config). That's increasingly unusual as people move to nginx in containers, but it does still happen.

I have the impression (maybe mistaken) that the scriptable module story in apache is much more mature than with nginx. Apache has had mod_python, mod_php, mod_perl, mod_lua, etc for ages. If you're using nginx, then you're most likely proxying to a backend. I've used mod_lua and apache for an application server and infrastructure tasks to great effect. This is anecdotal of course.

No. In fact Apache has more than double the share of Nginx (32% vs 14% of websites).

Not everyone follows fashion.

Nginx is a pretty different thing. Its primary purpose is quickly delivering files on disk and acting as a proxy, specifically not executing custom code.

Apache is more like an application server framework specifically targeted at executing custom code (hence modules). It is a little obscure and old fashioned but actually quite powerful and very flexible/customizable.

Since many current server side frameworks (say Node.js and all other Swift frameworks I know) do not really embed well into the server but are HTTP servers on their own, Nginx is often used as a frontend server in such contexts. It is very good for that (and Apache often overkill).

Anyways, running your code within Apache has pros&cons, as always. But this has little to do with Nginx vs Apache. (i.e. it may still make sense to use Nginx in front of Apache hosting a mod_swift application).

People still use Apache for a lot of things... It performs just as well as nginx, and in some situations, like reverse proxy, is even better (more compliant). Talking about Apache httpd 2.4 of course... older versions weren't as good. Bad that's ancient history.