> a "this is great but tangential reasons why this does not fit one of my use cases" anecdote
I understand your point, but I suspect I'm not the only sysadmin-type on HN and that this might be a more common (to this particular audience) use-case than your thesis would suggest.
> Using these scripts does not mean you no longer need to understand "raw" commands
Sure, but the reality for many is that if you spend your working hours typing "sstart" and "sj" and "gc" and "ll" and whatever else in zsh with a billion plugins, one day you'll find yourself on a P1 call at 2 AM going:
>> oops, that's not it
>> erg, I guess I made an alias for that on my machine
>> what are the flags for ps again?
>> why did that glob delete the wrong files?
>> why isn't journalctl showing me all the logs??
etc.
Whereas if you have to type e.g. `ps auxfwww` and `journalctl -xel --user` a billion times a day, that will be locked and loaded when you need it. Even if you can't necessarily remember what all the arguments do. ;)
I understand your point, but I suspect I'm not the only sysadmin-type on HN and that this might be a more common (to this particular audience) use-case than your thesis would suggest.
> Using these scripts does not mean you no longer need to understand "raw" commands
Sure, but the reality for many is that if you spend your working hours typing "sstart" and "sj" and "gc" and "ll" and whatever else in zsh with a billion plugins, one day you'll find yourself on a P1 call at 2 AM going:
>> oops, that's not it
>> erg, I guess I made an alias for that on my machine
>> what are the flags for ps again?
>> why did that glob delete the wrong files?
>> why isn't journalctl showing me all the logs??
etc.
Whereas if you have to type e.g. `ps auxfwww` and `journalctl -xel --user` a billion times a day, that will be locked and loaded when you need it. Even if you can't necessarily remember what all the arguments do. ;)