Slashdot Mirror
Microsoft Next Generation Shell
An anonymous reader writes "I found this while searching for Perl Jobs in India:
"The Microsoft Next Generation Shell Team is designing and developing a new command line scripting environment from the ground up. The new shell and utilities, based on the .NET Frameworks, will provide a very rich object-based mechanism for managing system properties. To be delivered in the next release of Windows, it will include the attributes of competitors' shells (e.g. aliases, job control, command substitution, pipelines, regular expressions, transparent remote execution) plus rich features based on Windows and .NET (e.g. command discovery via .NET reflection API's, object-based properties/methods, 1:many server scripting, pervasive auto-complete)."
I liked this the first time... when it was called Cygwin.
--
"What do you want me to do? Whack a guy? Off a guy? Whack off a guy? Cause I'm married."
bashWinXP
KFG
Let me guess what's next down the pike: a /proc filesystem, a serial console capability, runlevels, and a package manager with dependency feature.
Hmmmm...
bound to reimplement it.
I don't know who said it. But it true IMHO.
Happy New Years to you all!!
assert(expired(knowldege)); core dump
Uh, I think they still need to fill this "hole" (pun intended). Perhaps if they try removing all those integrated services and make them modular, they might be able to lock down their OS to the level that most NIX's have enjoyed for years now. Think of it in terms of inbreeding...the more times you marry your sister, the weaker the blood becomes. Same thing with Windows. My sig says it all in regards to why Windows is so popular.
"Klaatu, verada, necktie!" -Ash
The candidates are as follows:
Command-line Remote-capable Advanced SHell (CRASH)
Microsoft Advanced SHell (MASH)
Synchronous Multi-user Advanced SHell(SMASH)
What is YOUR favourite?
Wow, a hugely complex scripting environment with hooks into every aspect of the OS.
.... Again!
Virus writers - here is your big chance to spread like wildfire through windows machines!
There are a thousand forms of subversion, but few can equal the convenience and immediacy of a cream pie -Noel Godin
Yea, really. Copying sucks. Damn those dickhole car makers like Porcshe and Ferrari. They're just copying Ford. And screw that guy who came up with e-mail, what a total rip off of postal mail. And those leeches over at NASA trying to copy all the ideas of science fiction writers. God. What a bunch of losers.
I'm Rick James with mod points biatch!
Microsoft: We Invented the Shell in 2003.
; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
Hasn't Amazon got a bunch of patents on this?
If you were blocking sigs, you wouldn't have to read this.
Unix has a wide range of controls over running programs, from the primitive to the advanced.
(i) kill can send signals to running programs.
(ii) Many running daemons watch their config files and reload them if they're changed (or, more primitively, when you send a -HUP with kill to them).
(iii) Other programs use a form of message passing, in which you drop messages in mailbox/spool directories, and the program picks them up - e.g. mailers, print daemons.
(iv) X programs can have events/messages sent to them on the fly
(v) KDE prgorams can be controlled to a level of granularity similar to Amiga ARexx of yore via the dcop CLI command.
(vi) GNOME programs are scriptable in any language with CORBA bindings.
For years I've had friends who think I'm an idiot for not swallowing the blue pill (MCSE), and instead insisting on learning Linux and the requisite scripting languages to work in it.
It warms my heart to know that those brainless, cert-chasing mercenaries will have to learn Perl. Bwahhahahahaha!
It's not necessary to carefully avoid reading the very short page that this story is about. It's not necessary to make a (completely wrong) wild speculation that is trivial to double-check just by glancing at the final line of the job posting. It's not necessary to embarass yourself in public. The final sentence of the job posting says:
Of course, this is the first time anyone on Slashdot ever posted something incorrect without reading the story in question, and doubtless no one will ever do something that silly ever again.
Professional Wild-Eyed Visionary
behold, the MS 40 year unix-recreation plan!
Unix sux. lets hack out all of this bloat.
Hmm. actually, I guess that GUI thing wasn't so bad after all.
Thinking about it, I guess those long file names were quite a neat idea.
On reflection, the whole multi-tasking thing was fairly useful too.
Hmm. server admin. tricky stuff. lets see if we can't crowbar that back in too.
Right, in another ten years, with all these super features in place we'll have a whole new product...MSnix is born!!!
Maybe as part of this next-gen shell they'll introduce a good command line text editor.
What do you mean 'maybe'? Windows XP Pro already has edlin.exe, what more do you really need?
(Sometimes, backwards compatibility goes too far.)
--Dan
Another proof comes from that site:
:-)
You can download the huge current tree in standard gzipped tar format, but be warned: it's about a megabyte right now.
IIRC, Microsoft didn't warn us explicitly before downloading the 100 Mb Service Pack for Windows XP.
Beware: In C++, your friends can see your privates!
Ok, let's see how to copy a file...
v e1:> File fDest = new File("test2.txt");
System.LocalDrives.Drive1:> copy test.txt test2.txt
copy: Unknown namespace
System.LocalDrives.Drive1:> System.IO.Copy("test.txt", "test2.txt");
System.IO.Copy: Type mismatch at parameter 1: expecting System.IO.File
System.LocalDrives.Drive1:> using System.IO;
System.LocalDrives.Drive1:> File fSource = GetLocalFile("test.txt");
System.LocalDrives.Dri
System.LocalDrives.Drive1:> Copy(fSource, fDest);
Wohoo, I did it!
Beware: In C++, your friends can see your privates!