Seriously?

As you can find below, using IIS can be forbidden by company policy. And I totally agree with that.

Installing Apache on Windows, it's quite a trick. Fortunately, I'm not a windows user, but as far as I know, it's not so simple to find Apache on Windows, there are a few different builds of it.

And Installing nginx which will work with IRIS, even requires building it from source code, according to InterSystems Documentation

So, yes. I'm strictly staying with my position. That even installing a webserver may cause pain. And on top of that, if it will require a production-ready configuration, with restricted access, became even trickier.

The fact that it's still available in the Community Edition, does not mean that it will not be removed there too. And I'm sure not all developers, can use Community Edition in development, because, not all features are available in Community Edition, and it's very limited by the size of the database and connections (even after increasing). So, for most of the customers, it's rather impossible. But now, InterSystems I would say forcing to use it in development by any developer. So, I see, no reason of pushing Community Edition as an option for developers. It's a good alternative, but useful for a minor part of the developers.