4 ms·
Anecdotally this has been my experience. Just one sample size out of many but I do prefer working with people who share an affinity for CLI.
by xfitm3 6y ago
Anecdotally this has been my experience. Just one sample size out of many but I do prefer working with people who share an affinity for CLI.
- Jtsummers 6y agoI don't think it's an issue of talent. But a preference for GUIs often hampers people and the work they support. You can't compose GUIs like you can CLIs, and that's important as your workflows become more complex and need to involve more things. You can either extend the GUI (Hah! only if you own it or it's open source) or develop manual processes, or use tools that can automate GUIs but tend to be fragile.
- oblio 6y ago> You can't compose GUIs like you can CLIs You can, actually, but few companies bother to do it. There are quite a few apps with macro functionality, where each GUI option is also a command and you can record those commands. I imagine they have too few users who use that functionality so that's why they're so rare.
- ByteJockey 6y agoBy compose I think they meant use two different guis in the same workflow, sort of like how you can pipe the results of one command into another.
- pjmlp 6y agoAs mentioned on a sibiling thread, when I started in computing CLI was the only option and I don't miss those days. Xerox Computing / Lisp Machines >>>> UNIX CLI My affinity for CLI boils down to Powershell capabilities over classical UNIX shells, including having a REPL and debugger.