Linked by Adam S on Tue 8th Jul 2008 12:47 UTC
Talk, Rumors, X Versus Y In 2006, Microsoft released Windows Powershell, a new command line shell that, via cmdlets, scripts, and executables, allow core system administration tasks to be scripted. While this functionality has been available on Unix-type systems for decades, Microsoft's version will almost certainly, within a few years, be available on several hundred million PCs. So how does the Powershell stack up against Linux favorite bash? MSDN links to this Bash vs Powershell article.
Thread beginning with comment 321933
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: .. and then some people say....
by Nex6 on Tue 8th Jul 2008 15:26 UTC in reply to ".. and then some people say...."
Nex6
Member since:
2005-07-06

if your a good windows admin, then your used to scripting things. Perl has navtive windows support. you can also use vbscript. hell even python,

the main point being, just becuase your in a windows shop does not mean your brian dead and dont script anything. the only way to effectively maintain a large number of workstations and servers is *with* scripting. i have so many scripts in a few different langages, its not even funny.

and, the other admins, and IT guys i know that work in like enviroments are like wise scriptors. tho to be fair, most of us maintian or have maintianed *nix, so we carry over practices we have learned.



-Nex6

Edited 2008-07-08 15:27 UTC

Reply Parent Score: 2

stestagg Member since:
2006-06-03

'you're'. It's 'you're', not 'your'.

but more seriously, the problem with Microsoft, in this context, is Technologies, IMO.

The *nix world works to the Keep it [the implmementation/interface] Simple principal. This makes the difficulty of solving your problem pretty much linear to the complexity of the problem. Of course, the lack of 'fluff'[typically GUIs] means that the barrier to entry is usually slightly higher with this philosophy

Windows, on the other hand, seems to subscribe to the 'Technologies Technologies Technologies'[Developers, Deverlopers... ;) ] philosophy. They then have to re-create new interfaces to interact with each new technology.
So the barrier to entry is lower, because you are using a customised interface that is simpler to understand than an abstraction, but the moment you try to do something that the interface makers didn't anticipate, then you hit a brick wall. And with MS, this is usually a great big ugly 1000ft brick wall.

Maybe my perspective is skewed, I've just finished writing a spam filter for Exchange 2003. Anyone else thinking of doing so. Dont. Ever.

Reply Parent Score: 1

Nex6 Member since:
2005-07-06

.... never said I was an english major.... ;)

I agree to a point, on Nix, systems interfaces and such tend to be very simple. like bash, its simple useable. and; allows any other shell app to work with each other. the differance between powershell, is MS wanted to also pass arround objects. and interact with dot NET. with strong security built in the "shell" intself.

now, you can not do that and; keep it very simple. there has to be some complexity in it. and powershell has a roadmap, so remoting, and all sorts of stuff is on the roadmap.


microsoft has this thing where they sometimes want to "help you out" as a developer. and that, is where the problem is sometimes.

-Nex6

Reply Parent Score: 3