The problem is that without understanding the "arcana" of the OS platform you're using, you'll quickly hit a brick wall with your IDE. You won't understand what the configuration options mean, you won't understand what the documentation or people on StackOverflow want you to do and why. IDEs are mostly an abstraction over a set of CLI tools; if you try to do anything nontrivial, you'll see where the abstraction leaks.
This is true of quite a few of the kludgy build-an-IDE-out-of-plugins environments popular in the open-source world (Atom, VS Code, Vim-as-IDE, etc), but that's precisely the problem I'm getting at.
It doesn't tend to be true of mature IDE-first environments (see the aforementioned Visual Studio or IntelliJ).
I'm talking strictly about mature IDE-first environments. Visual Studio (which I use daily for C++ development), IntelliJ (which I used for Java some time ago) and AndroidStudio (i.e. IntelliJ with plugins, and it's probably the most leaky abstraction of an IDE I've ever seen).
