I agree that the article is flawed, but not for the reasons that you mention ... the article is flawed because it claims that there is a problem with IDEs, and then it goes on to describe a problem with the deployment of the app and its services on a local development workstation, so the hassle of setting up and maintaining a local test/dev environment - THAT is the problem at hand ... so, clearly, and obviously, this is not a problem with the IDE as such, therefore the title of the article is a misnomer IMO.
So the issue is not one of "IDEs being stuck in the past" or whatever nonsense - the problem is with the burden of setting up and maintaining a test/development environment on your "local" machine - and the solution (supposedly) is to move that environment into the cloud (which at the same time also makes your dev environment portable across machines, if for instance you want to access your stuff "on the go").
So that is the problem to be solved (if we assume it is a problem) ... "cloud" would be one answer to that, Docker and so on are other solutions. The question where your IDE runs and what it looks like, whether it's browser based, or a desktop app, or whatever, is really inconsequential, as long as you have a mechanism to get at your "stuff" (source code and running app) in the "cloud" or in "Docker", or in whatever environment it runs.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I agree that the article is flawed, but not for the reasons that you mention ... the article is flawed because it claims that there is a problem with IDEs, and then it goes on to describe a problem with the deployment of the app and its services on a local development workstation, so the hassle of setting up and maintaining a local test/dev environment - THAT is the problem at hand ... so, clearly, and obviously, this is not a problem with the IDE as such, therefore the title of the article is a misnomer IMO.
So the issue is not one of "IDEs being stuck in the past" or whatever nonsense - the problem is with the burden of setting up and maintaining a test/development environment on your "local" machine - and the solution (supposedly) is to move that environment into the cloud (which at the same time also makes your dev environment portable across machines, if for instance you want to access your stuff "on the go").
So that is the problem to be solved (if we assume it is a problem) ... "cloud" would be one answer to that, Docker and so on are other solutions. The question where your IDE runs and what it looks like, whether it's browser based, or a desktop app, or whatever, is really inconsequential, as long as you have a mechanism to get at your "stuff" (source code and running app) in the "cloud" or in "Docker", or in whatever environment it runs.