Yeah, with docker it will be easier to offer a working environment

And we already have a lot of open-source projects, based on docker. But switching most of those projects from Community Edition to normal now will require additional configuration, on adding webserver container next to IRIS. And I think we should think already about it, and produce new projects, even on Community Edition, with WebServer as well. So, it will be easily switched for any reason.

Yeah, I would not expect less, from such an experienced man. But, I'm mainly worried about beginners. 

Offical Apache, does not offer any builds for Windows, it offers using 5 third-party projects, one of them with a dead link. And even mentioned by offering 4 different builds of the same version. And not everyone can easily decide which version is needed.

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.

I mean, a lot of stuff still really depends on a web server. It's quite difficult for a beginner to do anything useful, having bare IRIS, without any web server. SMP is a dependency, Atelier API is a dependency and so on

But it should be a bit more gentle way, first of all, remove any dependencies of this, or make them at least optional. 

Yes, they already mentioned that in another post

But, how knows how long it will last, the later version may remove that support

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.