Kind of, but in practice they probably aren't going to use those unless they're already committed to the Java world because they're slower, less compatible with the extensions they're probably using, and fewer people use them so you're more likely to find bugs or gaps in documentation. Again, I'm not saying that Java is terrible or that nobody uses it but simply that the community is smaller than the entire tech world — especially after Oracle's sales pressure — and that means that any given project has a greater chance of not having enough support unless a major company backs it.

Each community is tiny when measured against the whole tech world, not really getting the point.

A C++ shop couldn't care less about what a Swift shop is doing and so forth.

The point being that Java-specific things like WARs, Tomcat, etc. were almost exclusively used by Java shops whereas more general tools such as httpd are used across multiple communities. A C++ shop can host their app behind httpd/nginx/etc. the same as a Swift shop even if they don't otherwise use the same tools.

A C++ shop was most likely using COM or CORBA back in those days, I really don't get that insistence with httpd.

So, our startup created a mod_tcl similar to AOLServer, basically a TCL Application Server, no else got to use our tooling besides our customers.