6 ms·
For me, it was needing/wanting ZFS. I still don’t like command line stuff generally, because there’s a sort of tension between the different needs for the CLI
by Modified3019 3y ago
For me, it was needing/wanting ZFS.
I still don’t like command line stuff generally, because there’s a sort of tension between the different needs for the CLI being a tool for scripts to interface with, and a tool for humans to interface with.
No complaints about the scripting aspect, that’s all good as far as I care. In fact I would consider that the rightful priority. But there’s problems when using CLI tools as a human manually.
If I want to unpack an archive via CLI, well I only do that intermittently enough that I (who has poor memory) will have to look and parse the options every single time to make sure I’m doing it right. Also, most of the included manpages are obtuse dogshit intended for an audience that is absolutely not me (and I suspect it’s also not intended for anyone except the program author). I end up just googling “how do I x” and copy and paste, which is UI failure in my view. There are alternative manpages which provide task oriented examples, but I tend to forget that’s even there.
CLI programs just don’t have a way to at a glance tell me that I actually need whatever “-r” or “—foo” does, which makes them much slower if I’m doing something only once in a while.
I use ZFS commands all the time so I remember those mostly, but everything else rapidly fades.
Navigation through directories is also a pain I’ve never found a way to make better and faster in a way I can remember.
- Given_47 3y ago> Navigation through directories is also a pain I’ve never found a way to make better and faster in a way I can remember. Zsh auto suggestions make it a breeze for me. Also cd -n to cd to the nth ago directory in the directory stack. If you’re referring to ridiculously nested directories for a one-off visit tho, yea I’ve also been trying to find a better solution lol