Liking using something is a bit different than having to use something. Are you saying you don't think the majority of developers need to use the command line for things like git, npm/general dependency management, running local web servers, compiling apps, continuous integration, etc...?
Again, I'm not talking about what's more powerful, and I'm not saying that everyone works this way, but I am suggesting the majority of developers do need the command line to do their job.
Unfortunately, I'm not aware of any usage statistics for the command line in isolation. But if you look at the most popular technologies, e.g., Node[2], then you can most likely extrapolate that the majority of developers are working with the command line.
CocoaPods, Carthage, Fastlane, git, all require the command line, and most teams use some combination of those. Not to mention Xcode literally is just a wrapper around Unix processes like `xcodebuild` and `SourceKitService`. Then there's a whole host of other support command-line utilities for doing Cocoa development like `codesign`, `xcrun`, and `xcode-select` off the top of my head.
Again, I wasn't making argument about where developers spend most of their time. Just that they need the command line as part of their workflow.
How many processes an IDE uses is an implementation detail.
The large majority of Apple and Microsoft developer communities live on their IDEs as part of our workflow.
Scripting and automatization can be easily done from the IDE as well, thanks to macros, REPL and build integration points.
Dropping down into a UNIX like CLI is the exception, not the norm for a large community.
Ah, but what about WSL? Well, Microsoft saw a market opportunity to win developers that buy Apple computers to do Linux work, instead of buying laptops from the likes of Dell/Asus/Tuxedo/system76 to start with.
So they are making UNIX devs comfortable on a foreign platform, just like NeXT was built on top of UNIX to take a piece of the pie from the UNIX workstation market being lead by Sun.
Using the shell was never a thing for NeXTSTEP nor classical Mac OS development workflow.