Honestly terminal commands are like a picky voice assistant that you talk to via keyboard... you tell the computer to do something and it just does it, or it fusses at you that you screwed up something.
Clicking stuff ends up being the slower way once you know what you are doing...
At some point, I realize that I'm furiously clicking the up arrow twenty times just to reenter a command that was two words long anyway and far quicker to type out. Not even CTRL+R would make it more efferent than typing.
Even with mid-command matching, like "ctrl+r Doc" for "cd Documents"? Just in case not everyone has found that you don't have to match from the beginning of the string you're looking for.
Hmm, now that I think about it, I want to say a GUI provides a (potentially false) sense of security.
At the very least, it gives an intuitive sense of direction, so that you can use a program with very little understanding of it. Things like Handbrake over ffmpeg I'd prefer over having to look up how to do 2-pass conversions online every time I want to make one.
The menus tell you all of the things it can do in a relatively intuitive way. It's easier and quicker to get started than reading the help/man page and remembering commands. Much shallower learning curve -- but of course, a much lower ceiling on what you can do as your proficiency grows.
While I love using a terminal, there are certainly things that I prefer a TUI or a GUI for. But they should be navigable using the keyboard. I can move files around much faster using Total Commander or Midnight Commander rather than using the terminal.
no, you can literally dictate what to do without having a computer in front of you..
On Windows, try to remember in which window, page of that window and which button to click to change anything.
Basically me whenever I try to use Linux on a permanent basis. What's that, you want to run a program at boot? You'll have to do it all in CLI and there's a pretty high chance you'll brick the OS. Oh, and don't make any spelling mistakes!
Not sure which distro you were using, but most have an autostart gui option and you would have to make some serious spelling mistakes to brick your system.
That's me with Git. If my colleagues need help and they're on the CLI, I can just literally spell them out everything they need. But if they're using some sort of Git GUI, it's always like, WTF are all these buttons? Are you sure, Git even has that many features? How do I tell it to do XYZ with certain flags? Are you sure, this isn't missing some Git features?
I think git's CLI is not a good user interface but with how ubiquitous it is as a VCS, it's better to power through the oddities and become proficient in it.
Yeah, I always tell new trainees, they can use a GUI, but they won't get around learning how the CLI works, as when they look anything up about Git, they'll only find commands.
This is myself with my colleagues. I use Lazygit and GitUI daily, otherwise I would spend a lifetime typing out numerous Git commands every day. And it is amazing how much one can do and how fast with these TUIs. But if a colleague needs something, and of course, they do not have these programs, all I can is just shrug and point them to the internet, as I have already forgotten all the little flags and parameters for more advanced commands. It is incredible how easy these TUIs make Git to use.
Well, cool that it works for you, but that is kind of why I stay away from the GUIs, too: I do not want to forget how the CLI works. Or even just become less comfortable in it.
When you need to look anything up about Git, you get told commands, and I need to mess with Git repos on remote servers every now and then.
Also, even if I can't help colleagues in their GUI, they generally have the CLI somewhere.
I do use a shell with type-ahead suggestions to alleviate the typing somewhat.