Linked by Thom Holwerda on Thu 25th Jan 2007 00:43 UTC
Microsoft "Once upon a time, when DOS walked the earth, the command line was the primary user interface for most of our computers. Then, Windows came along, and Microsoft seemed set on leaving the command prompt to dry up and wither into obscurity. Fortunately, Microsoft has again turned its attention to the command line and, in so doing, has produced one of the most compelling new Windows features eWEEK Labs has ever had the pleasure to test: Windows PowerShell."
Thread beginning with comment 205677
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Complicated
by axilmar on Thu 25th Jan 2007 14:17 UTC in reply to "RE: Complicated"
axilmar
Member since:
2006-03-20

The purpose of the PowerShell is to allow difficult tasks to be easily coded as scripts. It gives access to .NET, and therefore it can be used for programming scripts, .NET applications, and all kinds of difficult to perform tasks.

Reply Parent Score: 1

RE[3]: Complicated
by nutshell42 on Thu 25th Jan 2007 15:10 in reply to "RE[2]: Complicated"
nutshell42 Member since:
2006-01-12

Then they should have called it PowerScript or MS Visual ADVANCED or something.

But they called it PowerShell and it's quite shitty at that job. For 40MB of memory out of the box you get a shell that's overly complicated and less suited for many shell tasks than bash (or even cmd.exe).

It's great that MS finally made its own Perl/Python/Ruby clone to satisfy their NIH syndrome but in the meanwhile we're still waiting for a powerful shell for Windows without all the jumping-through-loops involved in using cygwin.

Edited 2007-01-25 15:10

Reply Parent Score: 4

RE[4]: Complicated
by twenex on Thu 25th Jan 2007 18:37 in reply to "RE[3]: Complicated"
twenex Member since:
2006-04-21

Right on.

Reply Parent Score: 2