For me, at least, I feel much more in control of what's actually going on when I'm working on the command line; once you hit the GUI level, there's another laye

For me, at least, I feel much more in control of what's actually going on when I'm working on the command line; once you hit the GUI level, there's another layer of abstraction that you have to understand and deal with that in a lot of cases isn't very helpful. Case in point, right now I'm an undergrad TA'ing a C++ class. One thing that has been very useful when helping students out is compiling their code under Clang and GCC, which for me, is as simple as just changing `CXX` when I cmake their stuff. But hell if I have any idea how to change that easily in their IDE. It's also easier for me to redirect compiler output somewhere so I can look at it, and for maybe everything except step-by-step debugging, I have pretty much no need for the IDE. Granted, GUIs can offer a lot of advantages - if I'm moving data between two different computers, I will almost definitely use WinSCP, unless it's someone I need to script, simply because the interface is clean, straightforward, and I've never yet had to worry about side effects. And obviously, I use a browser like Chrome and an email client like Gmail. But there are some things where the GUI just adds way too much complexity that I don't ever want to deal with.