Hacker News Reader

Comment by kukx | Hacker News Reader

One thing about PowerShell that annoys me is the verbosity and the use of capital letters in commands. While it is fine for scripts that you write once it feels suboptimal for daily use in a terminal, where I prefer the least strokes possible. Also the slow startup makes me often choose an alternative shell in Windows (CMD,bash).

View on HN

You don't have to type capitals, and you have aliases just as terse and understandable (?) as standard unix commands: gci, iwr, ri, etc. So you don't have to type them if you don't want to. The

But if you forget, it's nice to have them. And for commands at the margin of your memory they're entirely discoverable (including the aliases).

It's not necessarily obvious when you start, but it's actually super useful to be able to use and re-use all your skills for selecting and filtering data. Being able to 'get-alias | where definition -like *item' is a great way to discover the terse aliases for file operations, for example.

I know that there are built in workarounds ie default aliases and the case can be omitted. But it creates another set of problems related to documentation and code samples/conventions. The objects passing is great, but it is not enough for me, except for writing scripts. I guess there are ways to make it work fine as an interactive shell, but that is probably an extra customization and in some administrative environments it may not be possible.

Casing doesn’t matter for Powershell commands, but it certainly Improves readability. Aliases certainly help when typing commands, too.

I haven’t had startup speed issues with Powershell Core, but when I do, it’s usually because of commands in my profile (which it tells you about).

Pascal casing is traditional in PC programming world, since the MS-DOS days, Microsoft just went along with the culture of the platform.

Reply on news.ycombinator.com