PowerShell Team Blog

I agree with DavidACoder. At the beginning, when the idea of decoupling the PoSH from the Windows-specific code came to me - I was excited, but, after a couple of days trying to do this and failing - I was really disappointed.

One more thing you do that doesn't work on Mono - you call Registry API in a bunch of different places. Why you couldn't do the same thing with a config file?

Pash(PowerShellのオープンソース実装、他OS対応)開発が始まっている

Nice work Igor. That's an impressive bit of work. I want to commend the PowerShell team for carrying so much about interoperability for the two projects. It really brings up a much larger issue for you.

PowerShell isn't a money maker for Microsoft. You're probably not going to sell much software solely based on PowerShell. If you build your version of PowerShell you have one "feature". If Igor builds his version you still have one feature, with two different implementations. As a whole, the community gains nothing but you've doubled the amount of work. If Igor and you work together couldn't you make one implementation of an even better project? In that case, PowerShell is still revenue neutral (possibly positive because you need fewer paid employees to work on PowerShell) but it's a better, more full-featured product. I know I'm going through a standard open-source argument but with the kind of interoperability you're suggesting isn't that just the next logical step?

Don't get me wrong; I love that you're supportive of the efforts of Mono and Pash. If you don't move towards open-sourcing these products that's your choice. It just seems like everyone is doing a ton more work for programs that are free to start off with.

I agree with the other posters.  If only a few calls are all that keep PowerShell running on Mono, then do it!  Powershell being a Windows-only tool is the main thing that keeps me from being interested in it.  Why use Powershell when I can just write nice script code in something like Ruby that works on a multitude of platforms?

A from the ground of rewrite of Powershell that is only 50% complete that will always be behind the Windows-based Powershell - all because Microsoft can't be bothered to make their code use only pure .Net code?  C'mon guys.

There should be only one distribution of Powershell (preferably open-sourced like WiX) and it should be cross-platform.  Until then, it's no better than Windows-only VBScript in my eyes and since I work in multiple environments, unless it works equally in all of them, there's no point.

Igor Moochnick announced the first release of PASH , an open source implementation of PowerShell. (I

Congrats Igor, I have been watching you with this project for some time, and hope to see it successful and that many others will jump on board.