Linked by Thom Holwerda on Wed 19th Aug 2009 09:21 UTC
Thread beginning with comment 379604
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2005-10-10
Hi!
I'm sorry for mis-speaking about PowerShell. This entry started from some stuff I said on IRC, and which I extended before I posted it here, but forgot to remove this part.
PowerShell looks interesting, but I was told it tends to be verbose (and so not very effective as a shell), depends on the .NET run-time, and has not been ported to non-Windows platforms. It was also supposed to be part of Vista, but eventually was excluded (along with Avalon, XAML, and most other promising stuff).
A usable shell is not too critical for me as I tend to use it only for interactive use, in which case cygwin should be good enough, and if it becomes overly complex, I tend to convert it to Perl. You may choose Python, Ruby, or whatever instead naturally.
In any case, my criticism of PowerShell does not detract from the rest of my comment, which contains other faults I find in Windows, unrelated to it. So please take the time to read it.