3 ms·
I get it, and I respect the effort to clean up shell and create something coherent, but the commands and casing are really overdone and feel like old IBM mainfr
by speed_spread 4y ago
I get it, and I respect the effort to clean up shell and create something coherent, but the commands and casing are really overdone and feel like old IBM mainframe commands that require looking up a physical binder to use effectively. Start by replacing the commands with simple verbs like "walk", "filter" and "convert" and give them some default positional args.
I think a proper shell should still have a few shortcuts that break coherence for convenience, as long as there also is a long form for script readability.
- delta_p_delta_x 4y ago> Start by replacing the commands with simple verbs like "walk", "filter" and "convert" and give them some default positional args PowerShell commands (more accurately, cmdlets[0]) have a fixed Verb-Noun syntax. Get-ChildItem, Invoke-WebRequest, etc etc. [0]: https://docs.microsoft.com/en-us/powershell/scripting/powershell-commands?view=powershell-7.2 https://docs.microsoft.com/en-us/powershell/scripting/powers...
- speed_spread 4y agoRight, and that verb-noun convention reminds me of https://www.techtarget.com/whatis/reference/Common-AS-400-commands https://www.techtarget.com/whatis/reference/Common-AS-400-co... ...and it's not good. At least AS/400 commands had terseness to them. Those powershell commands are ok-ish for scripting but much too long for interactive shell sessions where you need to "explore the space".
- delta_p_delta_x 4y ago> much too long for interactive shell sessions There exist aliases[0] for the most commonly-used cmdlets. [0]: https://docs.microsoft.com/en-us/powershell/scripting/learn/compatibility-aliases?view=powershell-7.2 https://docs.microsoft.com/en-us/powershell/scripting/learn/...