Linked by Eugenia Loli on Mon 24th Oct 2005 04:14 UTC, submitted by Eric
Windows Ars Technica has posted a lengthy article on the new promising Microsoft Command Shell. It looks at MSH from the point of view of both coders and Windows admins.
Thread beginning with comment 50436
To read all comments associated with this story, please click here.
Python comparison is apt
by morganth on Mon 24th Oct 2005 05:47 UTC
Member since:

I'm happy Microsoft is replacing the old DOS shell with something substantial, but I don't like the idea of them getting all this hype by comparing their implementation to things like bash. Microsoft may call MSH a "shell", but it's really a full .NET runtime with [some] shell syntax.

bash doesn't behave like MSH by design, not by deficiency. You want to connect to a full object system, and have access to lots of different API calls? Sure, then use Python, or Perl, or Ruby, take your pick. Interfacing these scripting languages with bash is quite easy--just use what every UNIX tool does, stdout.

The idea behind bash is that developers will always have to at least read input files and write output to stdout or to files. bash allows the user to control where the input comes from and where the output goes to, in the form of pipes and redirects. Other than that, bash's only purposes is to fork off processes quickly, allow them to be backgrounded and foregrounded, and support niceties like globbing. For that reason, bash can be a lightweight C program.

Someone had similar ideas about Python, since coding a Python shell would just involve figuring out when to invoke os.system("...") instead of interpreting some input as Python code. I think the project was called PySh when I was looking at it.

Anyway, I guess we should be happy when we have to admin Microsoft systems, we'll at least have a bit more control.

Reply Score: 3