I just encountered another serious (in my opinion) deficiency in Powershell.
I have a "cron job" (scheduled task) and I want the job to send *all* the output to a text file, *including* all error messages. The only way I could track down an error in my script was to run it from the console and read the error message (in red) from the screen.
This is just one example where a potentially very powerful shell fails in critical situations. Object model or no, the Powershell team should *pay attention* to the needs of system administrators everywhere, not just the point-and-click/read the screen types.
And there's no good reason why migrating Bash users should have to go around the block several times to do things that have been extremely simple for years: