| Yes | |
| Yes, but... | |
| No, but... | |
| No |
| Yes | |
| Yes, but... | |
| No, but... | |
| No |
@evan Yes if you're familiar with it, as faster and more composable. But likely less discoverable (though it has gotten better with good help and complex completion).
A search by menu name is a must-have for me in GUIs nowadays.
@evan Each is better suited to some tasks than the other. You can do CAD with a command line but anything that visual is usually easier with a good GUI.
Likewise, tasks that are suitable for scripting are usually better done with a command line.
The best systems mix them, using each where it is more suitable and have done for more than 50 years.
@evan Depends on the task, as others have said. But as a general matter, the CLI is more powerful. Yes, but.
(I run Emacs both in GUI and terminal mode.)
@evan As an IT administrator, I've found that the best-designed software has a language with objects and verbs. The language may be surfaced in a CLI and/or and API. I'm sure the code underneath follows this design.
The GUIs for these apps are layered on top of this and provide easy access to more complex actions with lots of options, the one case where a GUI is superior to a CLI.
@earth_walker you're a good sport, to respond so well to my lazy teasing.
Thanks for the detailed answer.
ed). but a lot of people prefer a TUI (like nano).ranger).crosspipe), I feel like a GUI is infinitely better than a CLI. you could implement the same operations in CLI, but it would not be the same category of application.@me @evan Hmm. This i my first time hearing of such a thing, or such a term, anyway:
https://en.wikipedia.org/wiki/Text-based_user_interface
Obviously, I've used such things many times.
For decades I have said a single-letter command-line option is all any user needs. Or deserves.
@evan No, but
- CLI tools are scriptable by design, and sometimes you need that. So that counts as “better” sometimes.
- Most CLI tools could have a GUI built around the core library (you DID build a library at the core, right? Text is not an API contract…)
- CLIs are the wrong tool for many things. Like most git operations on non trivial repos, where a GUI dramatically reduces the incidence of all sorts of errors.
@evan I liken command line interface to speaking and GUI to showing. CLI is more powerful, but whenever GUI is applicable, it is also more convenient.
Voting "yes, but" with the logic that if I had to choose to live in a world where only one is available, I would choose CLI -- even though I probably use GUI more right now.