Should have mentioned that while PowerShell is generally better at handling the pipeline and variables, and gives you access to the .NET framework to use, its not exactly speedy. It's a tradeoff

You should learn more about what you're mocking. The long names are for scripts and people learning to use the shell.

Get-ChildItem -Path $home | Where-Object -FilterScript { $_.Length -gt 2KB }

or

ls $home | ?{ $_.Length -gt 2KB }

In v3.0, it gets shorter because you don't need the { } or the $_ for the filter expression. So it's more like this:

ls $home | ? Length -gt 2KB

I won't try to claim it's perfect because it's not, but it's better than Bash (though it owes most of its heritage to Bash et al) because you don't have to drop in awk and sed commands to parse the output of the last command in the pipeline. Though pointing that out will probably get me flamed.

Sigh.

PowerShell has the concept of pipes, and takes them a bit further than *nix because the stuff that moves along the pipeline is an object. You don't need to parse it, because you can query against its properties. Get-Process | Sort-Object -desc cpu | Select-Object -First 10 Get a list of processes, sort by the CPU property on each one, then get the first 10 in the list

I'm sorry, Firefox just looks all candied out and simplified. Like something that people who finally started using 'Linux' in 2002 or so would like.

Now, that sounds elitist