On PowerShell

I want to start using PowerShell. Really, I do. I want to, as Alton Brown so eloquently phrases it, "put the spurs to it" and make some really nifty tools.

Problem is, every time I think to myself "this calls for PowerShell", I find myself heavily mired in clunky cmdlets and wondering if there's a Perl module in CPAN that would do pretty much the exact same thing.

Really, PowerShell wouldn't be necessary if Perl came installed by default on Windows. More to the point, PowerShell would be completely unnecessary if somebody would hurry up and write Perl.NET the same way people have leveraged Iron Python and (I believe) Iron Ruby.

I'm not 100% sure, but I think someone's already working on it. Either way, I don't mean to dump on PowerShell. It just seems like it is trying so very hard to eat Perl's lunch, when in reality Perl has already cleaned its plate, gone back for seconds, paid the check, and left the restaurant. Having to instantiate everything with "powershell .\something.ps1" and trying to work around all the little gotchas that arise when you start one shell, spawn another, get data back, and do all of this remotely on an ever-growing succession of machines. When the chips are down, I default to Perl because I'm comfortable with it. It's familiar and I know where it's going to bite me.