One criticism I've seen and levied myself is the sheer amount of typing:

[PS] C:\> Get-MyReallyLongFunctionName -Server furtle

$ lol --floop

PS is fine but it takes ages for the bloody thing to wake up and notice command completion. It is like dealing with a teenager in bed.

Actually, I have no problems with PS but with MS's idea of search as deployed to users.

(I run KDE on Arch. Search is faster than I can blink)

Verb-first was also a bad choice. When I type “get” I am getting thousands of suggestions which makes autocompletion pretty useless. There is also no way to find all cmdlets that deal with active directory. It would be much better if I could type “AD” first and then get all cmdlets that deal with active directory.

Try:

  man *-AD*

You want Get-Command here, usually, not Get-Help.

I don't think it's that bad. Better than bash where every command has is either something archaic or just what whoever wrote it wanted it to be. It better resembles English than the other way around. Plus you can use "get-command "something`" which gives you everything that contains that string, or search for a certain provider for all commands related to a specific thing.

Autocompletion still works, just type first letter or two after get and filter most stuff out.

Powershell was made to allow launching arbitrary programs with redirections and pipes. That's why some language choices were made and that's why I'm interested in comparison with bash.