3 ms·

Powershell is a pretty neat scripting language, especially if you manage Windows boxes or have lots of .net stuff around. It's not a good interactive shell env

• AnIdiotOnTheNet 5y ago
  I disagree. Yes, the syntax is verbose so that you get sensical names instead of things like 'awk' and 'grep', but that isn't a big deal because a) tab complete[0], and b) user-definable aliases. [0] tab complete works on cmdlets, switches, and variables.
  • Arnavion 5y ago
    And if one misses the short incomprehensible aliases, the common commandlets have those by default anyway. `cat` is `gc`, `grep` is `sls`, `ls` is `gci`, ... Same for switches and parameters. You don't have to miss `rm -rf foo/`, it's just `ri -re -fo foo/`
  • JadeNB 5y ago
    > [0] tab complete works on cmdlets, switches, and variables. Isn't this how modern tab complete works everywhere? bash 5.1 (the shell I happen to be running right now, and which I mention because I think of its out-of-box tab completion as pretty basic) tab completes variables.
  • pxc 5y ago
    I don't mind the verbosity at all, but PowerShell in my experience is painfully slow for interactive use, if you want the kind of niceness you can get with Fish, Zsh, or Elvish (fuzzy filtering, smart-case completion, any-order/substring completion, etc.). The module system is also not great for distributing little configure snippets like Oh My Zsh or something, it's clunky and over-complicated for that.