Software companies can't do software either. It's draconian masters that force usability on programmers that would be happy if the world ran on CLI. You know its the truth, or you haven't really worked with programmers before.
We have one guy on our software team that this describes. The rest of your post is condescending assumption that ALL of us have the unix beard and vim editor of that one dude. Paradoxically he is one of the iPhone owners in our Android heavy group. In conclusion, I guess I've never really worked with programmers before.
The software companies that produce the best UX don't do so because there's a "draconian master" forcing the programmers not to just have Macs boot directly into Emacs and give users electric shocks when they click the mouse button. They have teams that are actually interested in UX design. Everyone I've met doing engineering at Apple cares about this sort of stuff. And while I'm sure there are programmers out there disappointed that their Android phones don't boot into console mode, none of those programmers are people on the Android team who have only been held back from doing so by the Iron Fist of Sergey.
The CLI makes it easier to force developers to separate the functionality from the user interface. You still might have the guy that puts all the code inside Main( string[] args ), obviously, but at least that code is easier to test.
Just like removing the presence of alcohol from the alcoholic may allow him to resist temptation and become a better person, removing the GUI from people with bad GUI coding habits may allow them to resist temptation and write better code. But maybe not.
It also helps you discover who actually knows how to write software, and who is dependent on the development environment to erect all the scaffolding for them.