I'm going to have to disagree. Command line tools can be composed and allow you to do more than the original tool builder provided as well as make it easier to automate tasks. I find it very frustrating to work on systems when everything needs a custom GUI to interact.
I think the point here isn't that command line tools are more powerful in general, its that building a GUI gives that access to more users who aren't as comfortable with the command line.
If you don't like the GUI or want to combine into scripts the command line is always there behind the GUI.
That's fair. Sorry, my "GUIs rule" knee jerk reaction flared up. There are a lot of bad GUIs that can give the illusion of helping users, but place upper limits on what you can accomplish. I have been frustrated by various hacked together UIs on top of Linux package management and wrappers around source control tools.
No worries, I understood where you're coming from. I partly agree with you: I switched to git at the command line from tower because I wanted to script some features (and understand the tool better), but having the GUI there made it easier for me to get used to git in the first place. (though admittedly, tower is one of the good GUIs which make it easy to do a simple task, too many of them do the opposite)