3 ms·

Sane and consistent are two words I would never use with Powershell. Well, it's consistently insane, but I imagine that's not a typo. Or-Do-You-Enjoy-Over-Verb

• ygra 12y ago
  You do realize that PowerShell is case-insensitive (you don't need to hit Shift unless you need it for something like parentheses) and there are aliases to ease typing when you're just using the shell? (I wouldn't recommend using aliases in scripts, though.) Besides, if this is about command parameters, all that's needed is the dash and enough letters so the parameter name is unambiguous; for many common commands that's not longer than the single-letter arguments to Unix tools. And they are case-insensitive, too. No need for Shift here either. But perhaps you do enjoy the haphazard mix of /parameters, -parameters, --parameters, /p, -p with varying ways of specifying arguments to those parameters, like /x:foo, /xfoo, /x foo, /x=foo that can be found all over the place in the default Windows command-line tools (because that's what the argument was about here). In that case, yes, PowerShell is probably a huge step backwards.
• nailer 12y ago
  You know, eg, Get-Process is `ps` and nearly every common command has two or three character aliases?
  • lmm 12y ago
    Aliases are the biggest enemy of consistency.