Now this is just not accurate Joaquin;

“And still, just piping objects is limited when you just want to get at the text”

The absolute sweetest thing about PS is that beneath teh covers you are pass OBJECTS around.

command | foreach {$_.getSomthing}

works like a charm.
Piping objects, not text.

so, get-Process | foreach{$_.ID} will spit out all the PIDs for the procs running, ala “ps -ealf” in my beloved *NIX.

Anything that is not a cmdlet can be cast to the .NET object of your choosing, and hence has the properties of said object.

You can pipe a cmdlet to Get-Member and see the plethora of methods and properties associated with the object.

For example;
Get-Childitem | Get-Member will return all methods and props associated with a file or directory object.

I do not mind the opinions, but be sure facts are straight to be fair.

HTH

L

In contrast to all the platforms, Powershell looks extremely resource intensive, and limited or cumbersome to program in certain areas. For example, short-circuit operations:

command1 && command2 # do command2 if command1 succeeds

And still, just piping objects is limited when you just want to get at the text:


command | awk '{ do stuff }' # easy
command | perl -a -e 'do stuff using $_ per line' # easy too
command | write "strings using $_" # fails in power shell
command | } # works, ugly


Notes: Web Site Mangling my Code, cannot do ampersand squiggly “process” squiggly combination.

http://backbone.lx.ro

If the environment is Windows centric, then the Powershell is easily superior.
If it is heterogeneous, then I would have to agree that Cygwin/Perl etc… ties the pieces together. Python has topped the list for me of late.

It is the age old argument. It just depends on the task of the day, and the direction of the group.

On that same note. Powershell is packaged with Exchange 2007 and also works with SQL 2005 SMO (SQL Management Objects).

It also plays nicely with Sharepoint, Active Directory, and will be bundled with Server 2008.

Also, I have found that rudimentary automation in Windows with Powershell can effectively cut out 80% lines of code.

What takes me 200 lines in VB or Java, takes 20 lines in Powershell
(It took MSFT until 2006 to get it going, vs. 30 yrs ago in UNIX LOL!!).

freyk, please let me know what you found to be far superior in function, as I too am interested in knowing.

BTW, Cross platform is a no brain-er.

L