Windows PowerShell 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.

The problem with Power Shell portability is exactly the same as anything else Microsoft did with dotNet.

To be honest, I rly don't see a point of dotNet today, nor products developed in it. I do program in C# every day and I do love everything about it and I do like Power Shell a lot, but that doesn't stop me for being rational.

Peter in his comments above was absolutely right - Why .Net ? Why not VBScript or just plain C. Microsoft created .Net as response to Java, but unlike Sun which provided binaries and support for each platform out there, MS choosed to support only Windows and let the community do all the job on other places (luckily there are folks like Google, Novell, Igor...) and lets be clear, its a lot of job, it needs to be organised and standardised across platforms, not something passionate programmerers can handle the way it should be.

There are even open source communities like Portable Net (alternative to Mono) which develop *nx dotNet framework only to prevent MS hooking everybody to their proprietary .Net implementation and after tones of programms written in it, become 100% dependent on it, and thus MS Windows.

Its well known fact that MS is trying to kill all open source so you can't expect MS to officially support PS on linux.

And that situation really sux, because PS is probably the best thing MS ever did, and aside for its greatest side effect of eventual total removal of the worst shell that ever existed (cmd.exe) from the Windows, it most definitely wont go further then that when MS plans are in question.

AVI, its great to be a Powershell fanboi, but please take a moment to re-read your post. Where would Java be without the *many* frameworks and the community around it ? I dont code in .NET, so I dont criticise it - enough said.

As for Powershell being 'far superior to anything in Unix', please re-read a lot of the early posts from Jeffrey and other members of the PS team : they have drawn much of their inspiration from *nix tools, and freely admit that Powershell is a work in progress. Personally, I think its the best thing ever to come out of Redmond, but that doesnt mean that I am prepared to criticise everything else in the dev universe. Spend some time actually developing a true cross-platform application in Python or Ruby (Windows, OS X, any *nix flavour), then come back and tell me whether its 'far inferior' to Powershell.  

Disclaimer: I cut Perl for a living, on a Linux desktop, so I may not be completely impartial :)

Those who do not understand Unix are doomed to re-invent it. Poorly. - Henry Spencer

I use PowerShell to manage Wintel servers and virtual servers; with the VMware vSphere PowerCLI I manage vCenter and some aspects of VMs.

I think a PowerShell PowerCLI  for LINUX will help me a lot. I'll be able to manage LINUX based serves and virtual servers in the same method I manage everything else.

Doing it without having to learn another language is great. Since I'm still fairly new to LINUX, have had little time to master it as oi would like to, and no training budget.

PowerShell - AFSL (Another Scripting Language).

Can't Microsoft just settle on one scripting language and get rid of all the rest?  

It is absolutely ridiculous to think Linux, Mac, Unix, or any other operating system should change just for Microsoft.

Microsoft can't even get their JScript to do an HTTP file upload simply.  Calling a VB.Net program from JScript to do the aforementioned file upload can not be done simply.

Why does Microsoft waste the time of so many people?