the below is abour '51 IDEs, not Microsoft or whaever.

I have done ARM developemnt using an IDE that allowed 'parts replacement' with no complaints. That environment I would never change to commandline, simply because it worked. No such statement can be made about '51 IDEs

Erik's well known distaste for IDEs is justified by his comments, and I don't disagree with his previous statements, but I don't consider them relevant either, because they are too narrowly focused on the technical side (trees instead of the forest).

How often do I need to repeat this; I would use an IDE the very moment one came along that did not restrict me. Actually, at this time there is none that even can do what I need, even with the supplied parts as is.

There is another side to programming, especially embedded, and that's the economics of a project. An IDE is a way to reduce programmer costs, by bringing in junior level programmers who aren't comfortable with CLIs. Train them? Sure, but that takes time and money, and it's bucking the trend to rely more on tools and less on skill.
I hope you get some great experiences in hiring that "rely ... less on skill"

Perhaps Erik is blessed with large budgets and an unlimited pool of skilled programmers all with 10+ years experience. I don't have that luxury, so I look for tools that allow me to make better use of the resources I have, focusing on project development instead of command line syntax.
where in hades is the difference between "command line syntax" and "defining a project"? both require that you learn the lingo.

I am not "blessed with ... an unlimited pool of skilled programmers" but if we adapt a policy of "they do not know, so let us not do it" instead of teaching/training it will be a sad state of affairs once we are retired.

Erik