Codename "MONAD"

In one of the most overlooked cool things at the PDC (in my opinion, anyway), the new Command Shell that will be in Longhorn blew me away when I saw it.  I walked up to the booth asking if unix-like file aliases would be in the new shell, and was given a demo by the team that had my mind racing.

First off, file aliases are possible.  WinFS type queries are possible through new commands called “commandlets” that you can write.  Similar to the unix pipe, you can do this with MSH (Microsoft shell / codename MONAD) as well.  Query results are actually .NET objects, so you can do things like (Don't quote me on the syntax; I'm working from memory here):

$p = get/process FileName
foreach ($p) { $p.ToString() }

A rather simple example, but consider that you can do this from the command line!

You can do WinFS filtering through the “|”  symbol. MONAD can also export natively to: HTML, XML, Excel, or plain command text in either a Table or List format.

And....the commandlets are developer friendly.  You can make a commandlet by inheriting from the commandlet base class, and adding attribute tags to the public properties to make them parameters to the commandlet.  .NET handles whether the user types “-?” or “/?”, so you don't have to care anymore!

I was all set to post that I had attended DOS's funeral after the keynote on Monday, but I wasn't prepared for what was being created to replace it.

One last thing: anything can be mapped to a drive, and drives don't just have to be letters. (Ok, I lied - that was 2) The example I was shown was that the registry was mapped to a drive, and you could navigate it like any other drive, with the results being returned from the commandlet as .NET objects!


  • What we will need next is intellisense for the command line!

  • Yes we do!

    They're working on the UI last, from what they said in the breakout session on the topic. Intellisense was mentioned, and they do want to do it.

  • If they add intellisense, I wonder if they will add support for console apps via xml or something...That would be nice as well, I played the concept at one point but without more underlying access to the system console it wasn't possible to do in any serious manner.

  • I did see a GUI editor for MSH scripts; They did say something about possibly adding support in VS for intellisense. I imagine something like the right-click & run query for database projects in VS2003. Only "Run Command" instead.

  • Its possible, I think intellisense should be, optinonally, supported directly into the prompt, unfortunatly as best as I can tell MS has to do it.

  • I think it would be difficult to do a graphical popup, but perhaps they could use bash-style tab completion. Say for instance, I typed "get/" and hit tab, it should list all of the available nouns that I could put after the get/ verb.

  • I don't think it would be too difficult if they abandon the old console code. A console is, at its roots, a text buffer with speicifc properties, by this point it really needs to be upgraded for various other reasons, I don't think it is out of reach, but more a matter of if they are willing to put the effort in or not.

    However, tab completion would be acceptable, sometimes scripting gets to be rather complex and any shortcuts or helpers are valuable. I am really rather curious what all they can manage

  • Actually, this is all new managed code. That's what allows you to have everything returned as .NET managed classes. If you want the old console around, you can use it. However, if you want the GUI, or your own app with text-completion / intellisense, you can make it in managed code, and really it's just calling MSH behind the scenes. Really cool stuff...

  • So I suspected, but I havn't had a chance to play with it yet(Hopefully soon), its a matter of what kind of extensibility exists. Point is it should be possible, and probably not to difficult in that case, to provide a graphical popup(considering the shell probably exists in a window of its own), however its more a matter of if anyone will do it or not. Possibly within the msh it will be possible where it wasn't possible to write a app that could do that with the old console.

  • Also, when I said console i meant the console itself, not cmd.exe, but the console backend.

  • Excellent post! I think you are right about it being the most neglected feature at PDC. Can't wait to play with it!

  • Take that, dirty Linux hippies! Take that, Thieving Macintosh Republicans!

    Seriously, this is a wonderful thing. The shell has been one of the most lacking areas under Windows. I don't know how many times I've dropped into Cygwin or, before that, wasted time writing little C apps just to do basic bulk renaming operations and the likes.

    Any word on whether they'll standardize the environment across all Windows products, or is this likely to be a server product only? Will this be the standard shell replacement, or will we now have, cmd.exe and newthing.exe all living in parallel? I like choices, but Windows apps' ad hoc use of largeley-incompatible and cmd.exe is already a source of pain.

  • Currently, there's both cmd and msh. MSH is currently v. 0.3

    It will be supported for Win2003 and XP as well as longhorn. And it actually is msh.exe

  • Ewww. I'll take /bin/bash over that gobbledygook, thank you very much.

  • Microsoft innovates the bash shell. What is that quote about reinventing Unix...

  • p.s. -- I can hardly wait to see the name of the GNU version. MONAD... G...?

  • they more they deny Unix is dead, the more they imitate it - way to go MS.

  • After adding "X-Windows" features to his OS, MS is about to add .... a shell <:o)

    More thant 30 years after Unixes !!!

    I love innovation@microsoft.... what will be their next thing : write a java like portable platform with a new object language ? ;-)

    LOL !

  • Hmmm, why don't they just but rights to /bin/bash. It's an excellent shell script and would fit into the M$ model well. What is new is old. ;p

  • Um, this looks a lot more like a general purpose scripting language (with objects and the whole deal) than it does bash. Stop trolling.

  • Exactly McGroarty; what uses what shell and with what capability, and how do you keep it all straight, and how long will it be before everything you use is shell-aware? Great for the computing newbies of 2009, but by then we'll all be doing somthing else; No thanks, I'll pass.

  • Microsoft trying to copy *nix. Imitation is the sincerest form of flattery. I guess those ms developers finally figured out *nix is better!

  • Note that this page hit Slashdot @ 9:33 AM.

    I now introduce to you a barrage of MS-bashing..

    (Quite predictable, really)

  • the current cmd.exe does commandline completion - not true intellisense, in that I hope you'll be able to 'tab' through all commandlet parameters, with their syntax handily displayed.

    You want TweakUI to turn on cmd line complation or HLCU/software/MS/command processor/completion char - set to 9, restart cmd.exe

    Someone said 'unix is dead then they imitate it'.. well, MS has has simple completion and pipes, and command-line programs like unix for years, now they're doing something far, far more powerful.

  • It is now official - Netcraft has confirmed: IIS is dying

    Yet another crippling bombshell hit the beleaguered Microsoft community when

    recently IDC confirmed that IIS accounts for less than a fraction of 1

    percent of all servers. Coming on the heels of the latest Netcraft

    survey which plainly states that IIS has lost more market share, this

    news serves to reinforce what we've known all along. IIS is collapsing

    in complete disarray, as fittingly exemplified by failing dead last

    [] in the recent Sys Admin comprehensive networking test.

    You don't need to be a Kreskin [] to predict IIS'

    future. The hand writing is on the wall: IIS faces a bleak future. In

    fact there won't be any future at all for IIS because IIS is dying.

    Things are looking very bad for IIS. As many of us are already aware,

    IIS continues to lose market share. Red ink flows like a river of

    blood. ASP developers are the most endangered of them all, having lost 93% of

    its core developers.

  • You can run, but you can't avoid Slashdotting ;)

  • I don't see any M$ bashing.

    It's nice to see M$ get away from the "you will do it only one way" mentality.

  • Ok... I had done every thing they say in that report for about a year...

    And that in windows! Using Bash and python ported to windows...

    Whats the news here?!

  • Man... does this look like DEC DCL on a VAX?

    $p = get/process FileName


    foreach ($p) { $p.ToString() }

  • Not bad. (As in: Get rid of the worst of the monopolist baggage and popup annoyances in the default installs - MSN Messenger, etc. - and I will manage to enjoy this when I'm forced to. You know how it is. ;))

    "One last thing: anything can be mapped to a drive, and drives don't just have to be letters." -- So was this a conscious effort to copy the Amiga, or did it just work out that way?

  • This is THE definitive tool that was long-awaited by virus creators :-(

    If we trust the casual MS security level, this new CLI will allow modication of public classes and lead to hell.

    One of the most efficient shelter against non-binary viruses was the poor shell of MS OSs... since they needed high level apps (MW, EXL) or interpreter (VB) to release their lethal load!

    Not any more :-(

    "It is not a bug, it's a feature." (tm) M$

    Alas !

  • What's all this about Microsoft bashing, PWRXS? This isn't Microsoft bash. This is a new shell. Please read before posting, tiny-minded confused-person!

  • Looks like Korn shell with a few tweaks. Oh well, if you're going to nick stuff you might as well nick it from the best.

  • Here's what I'm curious about. Fellow .NET knowledgable people: They are taking code, compiling it to IL, and then maybe JITting it, as you type it. Does this not involve the overhead of a VM? Of course it does. Are they going to leave a VM laying around in memory all the time, or will you have to deal with startup times on your console. A VM is about 10MB. What about hte overhead of compilation/JIT.

    One of the great things about the Unix shell is it's extremely small footprint. It takes just under a mb for me to launch bash. Can they get an entire VM in just under a MB?

    And yes, lets not have that "but hardware is cheep" argument. My SQL servers are OUT of memory, they have 2GBs. This is rightfully so, as they cache EVERYTHING they can. Unused ram is wasted ram. But it means I have to sacrifice 10MB of that for a console.

    I don't see that as a fair trade YET, at least not when they're is a competitor that doesn't require it.

  • <i>It's nice to see M$ get away from the "you will do it only one way" mentality.</i>

    Well, as long as you do it <i>their way</i>, sure. This is still re-inventing the wheel. Albiet it, that wheel now runs on all monster trucks. But that begs the question: Do I really need a monster truck to drive to the office?

    Think I'll take the subway instead. It's efficient, proven, pollutes less, serves the greater public at large, and just makes sense.

  • This is great. Long a reason why I prefer Unixy environments. The talk about a GUI is sort of a step backwards. We want something very useful from a remote, textual environment (a la ssh and bash on Linux).

  • Jerry Haltom --

    I'd like to suggest you enable virtual memory on that SQL server. Then it won't MATTER if the shell is 10mb since when it's not being used, it's quite nearly 0mb.

    My consulting fee is in the mail, love.

  • Wow! This looks like a really great innovation from Microsoft! I'll let my developers know to keep an eye on this one.

  • "Those who do not understand *nix will reinvent it."

  • I have to agree that it looks like the virus creators are going to have a field day. I predict that Longhorn is going to get kicked right in the Monads.

    "Those that don't learn UNIX are doomed to reinvent it.......poorly."

  • 10MB of less than half a percent of that 2GB of memory. I doubt it's making an impact. Waah~~

  • While all developers will love this new Command Line interface, Sys Admin now have a new security worry....

  • I hate m$ as much as the next guy and love writing scripts in bash etc (at home).

    But there are always going to be M$ systems I have to WORK on and if they have MONAD I would be a hell of a lot happier.

  • finally there will be something decent to spawn.

  • cygwin works fine. kthxbye

  • " Take that, dirty Linux hippies! Take that, Thieving Macintosh Republicans! "

    - {snicker}

    MS is not so smart. There are already very user friendly distros of Linux that offer all of these same tools for free. Microsoft is throwing millions at re-creating (cylce testing) all these tools - which will cause them to look towards ROI (more sneaky and market manipulation tactics required).

    Basically they are plotting a migration path for their customers to Linux and I can't figure out why. You see, the average manager/CIO will spend thousands of dollars implementing Longhorn just to discover that the same tools are available in a free tool. Game. Set. Match.


  • I've been doing the euqivalent on Windows and Solaris with TkCon/tclsh for years.

  • "Good artists copy, great artists steal"

    -- Steve Jobs paraphrasing Andy Warhol

    MSFT is not blind. They see OS X 10.2 (and OS X 10.3), Mandrake 9.x, RedHat 9.x, and they know where the bar is set.

    MSFT has something that even Apple doesn't have: $40 billion cash.

    MSFT can afford to create ANYTHING. The Longhorn command line is only the beginning. What little we have seen and heard of Longhorn is only the beginning (ex. WinFS). Remember: MSFT has been planning the major features in Longhorn since 1993 (ex. Cairo). MSFT is going to release Longhorn in direct response to the threats posed by Apple and the Open Source community. MSFT doesn't respond to percieved threats with a "fly swatter attack" they pull out the 80 megaton nuke and say "Come Get Some!".

    Never underestimate Microsoft. The .NET technology suite should remind you that, when threatened, MSFT brings out the heavy stuff against that threat.

  • I'm a Slashdot regular, but damn, there are a lot of trolls here. For shame, zealots, for shame.

    Anyway, this is cool stuff. Yes it's "been done before" (epistemologically speaking you could say that about a lot of software), but what is important is 1) what MS had before, well, sucked 2) this is not your father's bash, this is integrated into the system platform/library itself. While bash/ksh are really nice and provide some high level programming features, that is nowhere near complete platform integration. Beanshell would be closer, but tell me, who is running a Java OS? Nobody. The integration is just not there (note: I am an enterprise Java programmer, and I use Beanshell frequently). Show me your bash/ksh doing native system calls and GUI hooks (I strongly suspect this sort of thing is/will be possible with MSH, given that it is apparently all running on .NET/CLR). To quote Dana Carvey doing Bush "na' genna' happen". The next most similar thing would be, oh, a python shell or something.

    Damn, at least be happy MS is doing something (anything) right. For all the crap flung at .NET/CLR, it is a gigantic step forward, and I sincerely wonder how Linux and Open Source on the desktop are going to tackle the mounting integration in the Windows platform (even if you accept that anything Microsoft is evil, the question still remains, what do you have to show to the user to meet the (potentially perceived) value). Mono is a good start, and KDE boasts tight integration within its own scope, but for Linux to be a usable desktop it needs more...perhaps, etc., can forge a unified direction here. Part of the problem is the "old school" being resistant to anything new - that will strangle Linux on the desktop.

  • Microsoft sucks and has to steal ideas and work on other peoples implementations to try to stay in the lead.

  • I think the changes to the windows file system goes well beyond leaving drive letters behind. If I understand the presentations correctly they are leaving the idea of file location behind. The file can reside anywhere and that doesn't matter, the key is what the file is. You search through stacks of file based on what they are as described by the metadata. Moreover it looks like all of the metadata is indexed so that these searches don't have to scan the entire hard drive. I think it will be cool to open up explorer, ask for all documents relating to development project 1, and having them all found in no time at all regardless of where they lie, whether its random locations in my filesystem, or in some other filesystem or network that you asked windows to keep an index on. My only hope is that it really works, maybe we need to wake for longhorn 3.0 before we really get excited.

  • "I walked up to the booth asking if unix-like file aliases" ... "..Similar to the unix pipe, you can do this with MSH.."

    Yup, UNIX is the real thing. Microsoft knows this. I don't see this as any better or worse than bash/ksh.. probably because I haven't used it yet. This is a good thing for Microsoft developers... or are they converted UNIX developers? :) Goes back to the old argument that UNIX developers are better than Windows developers. heh heh. Don't flame me, was just a joke.

  • The problem with too much integration, of course, is that MS might be accused of not respecting the term of the various Anti-trust settlements it's bound to...

  • I'm a so called "linux-hippy", this sounds a lot more innovative than anything I'm used to. If it lives up to the hype this guy has created I will be most impressed.

    Also this is great because *nix shells have stagnated in recent years without anyone seemingly encouraging new features or functionality. It won't take long for this kind of competition to push the shells I use into new leagues of functionality.

  • FAO "A non-Zealot"

    Not sure about other shells or other distros but KSH on both Redhat and SuSE has been able to do both for at least 4 years now.

  • Finally, Microsoft does what apple has been doing with OSAscript for years. WOW! You have to admit that bash and csh are both lacking in quite a few areas when it comes to writing robust scripts.

  • Now all they need is to open source the OS, provide me with the ability to fully customize every aspect of my system, basic network tools, some sort of meaningful support, stability, BASH, some sense of personal security....hmm...

  • As someone who has been working in PCs since CP/M-80 professionally, let me say that I am impressed. Not as impressed as I would have been if they had done this 10 years ago, like they should have, but still, very impressed. There have always been the add-on shells that have improved the old CLI, but being an add-on were of limited ability. Imagine being able to assign the registry as a drive and treat it as an I/O device! Export to/from XML, et al! Face it, MS has really done something developer/power user friendly. As for this being a rip-off off other systems, I find that funny coming from a bunch of Linux lovers WHO'S WHOLE OS WAS A CHEAP DIY COPY of real about derivative works with little imagination...

  • RE: Stephen Booth

    "Not sure about other shells or other distros but KSH on both Redhat and SuSE has been able to do both for at least 4 years now."

    I'd appreciate any links or references, that is very interesting if true.

  • .NET? WTF is that? ;-)

    Seriously, is anyone actually using .NET for anything?

  • GNU version?


  • Map the registry to a drive? Is that an invitation to hackers to screw up your machine? :? I guess if they can scew you now anyways, it really doesn't matter.

  • Who wants to (or rather doesn't :| ) start the gnome replacement for MSH. Its gotta be called GNONAD. It makes sense really...

  • I'm a UNIX user, and I'll admit it: bash really sucks. Everyone keeps arguing about how great it is and how it never needs to change, and the end result is something that's horrifically outdated. Before blindly flaming, re-read the original article. This is a much more sophisticated shell than bash on all counts.

  • Oh wow, now we can have a useful shell in Windows! Oh wait, Cygwin gives me bash, zsh, etc already. And UNIX has for years. I can't believe MS has been sitting there with cmd.exe for so long when every other OS had usable shells for years. Hell, even sh and csh are more powerful than cmd.exe, and those are older than I am.

    But seriously it'll be nice to have something better native to the system. I'd be nice if MONAD would be a bit more like the UNIX shells instead of a different beast altogether though. Difference for the sake of incompatibility is stupid - and common at Micorsoft. At least there will be a few neat built in to the shell with .NET and MS file formats (whether they should be built in or external program is another matter I guess, but oh well).

  • who need gonads? Oh, monad, my bad...

  • as a linux user i see this as a good thing

    as said before, giving windows devvers a shell like this means at least more semi-portable code. this puts them back in a unixy way of thinking, which will make apps easier to port over to *NIX (in theory of course im sure MS will think of some way to lock it in)

    what bothers the majority of linux people is not that this kind of thing has been around and has been incredibly useful for 30 years, nor the fact MS came up with something like it and thinks they're the all seeing all dancing crap of the world for doing it, but its on one hand they say '*NIX is obsolete' and they turn around and release something based entirely upon it.

  • they are trolls, they care not about facts.

  • Yes, it's Just Another Scripting Language(TM), but it would have been nice if Microsoft just used the REXX stuff years ago. After all, it was in OS/2 and Windows NT was originally called OS/2 NT. They already support *.cmd files in NT based Windows...

    It's "not another shell" to me. Although the shells for UNIX is not perfect, it is well known and powerful. In my opinion, they should just base their new shell on something which is in wide use, such as BASH and modify it for use in Windows.

    It would be nice to have something similar to pgbash (bash for PostgreSQL).

  • Imagine: mount registry as an I/O device, import pre-hacked, exported to XML registry, instant hacked computer!! Sweet! Thanks Microsoft!

  • Heh heh heh.

    I cannot wait to see all the point and click brigade when faced with a CLI. Shame they're not getting rid of the "my first computer" GUI while they're at it.

  • "Yes, it's Just Another Scripting Language(TM)"

    No, it's not Just Another Scripting Language. The point is that it runs on .NET/CLR which gives it immediate and native access to the <i>entire system API</i>. That is not something your typical standalone created-from-scratch scripting language has. The trolls in this thread seem to be along the lines of "MS HAS CREATED A CAR! H4R H4R STUPAD MS, COPYING OUR WHEELBARROW THAT HAS WORKED FOR 30 YEARS!"

  • just a piece of info .Microsoft used to develop things for unix . lol i know its funny. i used to work for a company that bought software that microsoft was developing for unix.You never now what is in unix now that microsoft put there lol. look into a company called proginet lol.

  • To Panama77:

    well yes, he _did_ get shot at the end of the episode but you cannot be sure he was shot _dead_, and i'm pretty sure he wasn't cause it would make the script pretty difficult to continue

    To B4rt51mp5on:

    maybe you's like to know that the guy who originally invented the series has been fired, that's why they feed us such crappy episodes lately!

    Wait... what's this? Another Microsoft forum?

    WELL PHUCK MICROSOFT, FREE KEVIN, LINUX RULEZ, we cant get infected by vbs viruses ahahahahah

    More slashdot fun for everyone :D

  • I don't know why I am wasting my time defending MS here, but these are really awful trolls:

    "Imagine: mount registry as an I/O device, import pre-hacked, exported to XML registry, instant hacked computer!! Sweet! Thanks Microsoft!"

    Imagine: tar -xf myhackedetc.tar /etc

    Sweet! Thanks insecure OS!

    Uh, wait, you can't do that because of security restrictions. Although MS is typically awful on security, I'd like to at least give them the benefit of the doubt on something as naive as this.

    A more functional system universally implies more security exposure, regardless. And just because the Inix security model works, doesn't mean it's anything necessarily to proud about, as it is rather primitive, and I'm sure all the various ACL systems being proposed will introduce similar issues into *nix.

  • Ok ok...Say you're in this MSH and you're copying a 17 meg file...

  • I find it really wierd microsoft had a lot of experience with unix. Even had password security software for it. But they sold it off. Now why didnt windows have more unix like security and stuf in it already?I was amazed when i worked for proginet that they bought unix software from microsoft.

  • the GNU version will be codenamed "GONAD"

  • > Seriously, is anyone actually using .NET for anything?

    Erm, yes. Not as much as it will be in the future (a lot of people are holding back because of compatibility issues with older OSs, but those will fade away to background problems in time, just like I don't really worry about the fact that I write applications that won't run on Win95 any more), but still quite a few.

    .NET is actually pretty useful: a managed code environment, giving you similar advantages to Java (and, yes, a lot of code will run cross platform), plus the ability to compile directly to native code when performance is critical.

    In the next year or so, my guess is it will almost entirely replace VB for rapid development of Windows applications.

    > Not sure about other shells or other distros but KSH on both Redhat and SuSE has been able to do both for at least 4 years now

    I've looked through the KSH manual, and can't see anything relevant. OK, there's a plugin API which would allow you to write plugins to perform this kind of work... is what you're referring to a plugin of some kind?

  • Windows sucks.


  • For the guy that mentioned that it looks a lot like VAX, well remember Microsoft hired a bunch of people from DEC a while back, actually a lot of the WinNT components come from the VMS/VAX era.

    anyway, i dont see why people get exited about marketing hype such as .NET and all this other crap.

  • Microsoft would clone Unix with its own minor tweaks if it could get away with it legally. They are more concerned about keeping with the "oooh it looks perdy and plays my games too" scenario. Don't get me wrong. This concept is great for designing ma' and pa' programs but when it comes down to it.. programmers need to care less about how perdy it looks and if the consumer is going to find the product with a thousand bells and whistles.. and just stick to strong, stable and efficent programming...

  • Welcome /. Readers. Hi CowbowNeal :)

  • You Windows guys seem to be rather easily impressed.

  • I am a troll, I don't care about facts!

    Seriously, do you think we are stupid just because we run another OS than what conformist yuppies want us to do? Reality is plastic per se, dude...

    Regarding M$' CLI: If this is anything like "Unix Services for Windows", I'll laugh even harder.

    And to the guys and dolls who believe bash et al is a simple and ancient scripting medium: $man bash

    Care to explain what "Monad" can do on top of what is already available in scripting? Manipulate the registry? BWAAHAAAAHAAAA!!!!

    *nix all the way, baby!

  • Two things:

    First of all, the GNU version will undoubtedly be named "MOGNAD."

    Second, a shell does not a *nix make. If they actually employed some *cough* memory management in an operating system for once, that'd be one thing. I think this will be a good thing for Windows power users who don't get freaked out by white text on a black background, but a shell doesn't make a system good.


  • Heh, pathetic. The Bourne Again SHell (BASH) used by most Linux distributions has supported that for years. I agree with all who say that a shell does not make a stable operating system. Micro$oft has put Command Prompt in their operating systems for years, and it is quite obvious that adding a 'better' one will not help.

  • I have no opinion on this.

  • The command line is the most powerful tool ever known. I have worked on Telnet(80X24) applications more than the newer GUI trend, for a long time.

    A Console application has, is and always will support tens of hundreds of more users than a GUI application.. primarily because there is only 80X24 = 2KB involved in each transaction.

    I have seen a CICS Application handle over 10000 concurrent users... something which only a super-web-server could handle.. and IIS is certainly not one of them.

    If people had concentrated on the Console as opposed to the GUI, mankind would have achieved more with computers than they have now.

    I am Happy for MS. If they finally are taking the command line seriously, they will make it great for Server Side developers like me and a trillion others who would agree that a <page down> is easier than a scroll bar.

    Go Command Line!!

    When In doubt.. Code.


  • Wonder why they picked a name that sounds so similar to Gonad?

  • It seems that Microsoft is slowly moving to UNIX, just like Apple did with MacOS X.

    If Microsoft release a Windows skin for Linux/BSD, they'll have the most secure Windows ever!

    This will be good news for MS users, and for the industry as well.

  • Graphical interface or command line? Use both!

    That's how Unix admins have been working for the last decade or so.

    It's really nice to see Microsoft implementing this feature in 2005 or so.

  • Hello !! I am Dr. TOBOT !!! and when I hear "MONAD" I think "PUERLY FUNCTIONAL" , but, where is the functions??

  • > Seriously, is anyone actually using .NET for anything?

    search monster for ".net"

    I found 1771 postings.

  • This will be interesting to see, and probably fun to use. However, by the time Longhorn comes out (206? 2008?) and is accepted by users at large, it is reasonable to expect that the OSS community will have created something comparable.

  • Mmmm :)

    That fun :]

    This'll be a great features, using objects under command shell .... never sawn that under any unix shell ....

  • > never sawn [sic] that under any unix shell ....

    You need to get out more, dude! Ever heard of the scheme shell? Ever heard of Python? It's been done already, but the *nix and open source worlds don't have a single "big brother" telling everybody that they have to do things his way.

  • You've been able to download a free utility for Window$ NT that enabled soft and hard links for years.

  • BASH for Windows? Why didn't you say so?!

  • Good lord a lot of you are being trolls for Halloween. 0H N03S ITS DE M1CRO$H4FT DEBIL

    Y'all need to get lives. *nix is a decent OS, but has its flaws. OSX is a decent IS, but has its flaws. And, yes, Microsoft is a decent OS, and it, too, has its flaws. Zealots, please don't throw stones from within your own glass house. In the end, each OS is just a tool, providing solutions that work for group that chose to employ them.

  • "drives that don't have to be letters" oooh

    sounds like someone at microsoft found out what an Amiga Volume Name was



    instead of


  • So if the Microsoft implementation of this is called MONAD, will the GNU clone of it be called GONAD?

  • It has been said already that all parts of such a shell already exist under other OSes. To add to those mentioned, here's the XML Shell:

    which is the best way to hack XML, period.

    And nobody has yet disproved the old Unix principle: "make your program do one thing well." A shell that tries to be all things to all people will most likely fail.

  • Try as Microsoft might it'd take a hell of a lot more than this to pry my hands of my Mac OS X/Linux bash shell & terminal to get me to do windows again. UNIX is far more advanced than this and has utilities that are far more advanced than anything Microshaft can come up with.

    I still use Windows 98,2000 & XP and Visual Studio 6 & .NET. Though i've been using VS .NET for a while now, i really still don't get what all the fuss is about it. So you have some new languages and you can do web services.. whoopdi do, talk to me again when I give a damn.

    Microsoft is finally trying to come up with stuff now that Mac OS X & Linux have had for years. They are catching up... by the time Longhorn finally arrives Apple can put out 2 more releases of Mac OS X and Linux will have advanced so much. Face it Microsoft is loosing on the OS innovation front.

  • Yeah, a M$ shell. Ok.

  • Embrace and extend 25 years later. Well done :P

  • So basically this thing is more or less a version of perl or python running as a shell. Native API hooks blah-blah - perl has them too and I'm sure python does as well. Sure, it uses .NET extensively, but how hard is it - really - to write a .NET module for perl or python? Or for that matter a linux 'perlshell api' kernel module? Surely it'd be done well before xmas this year.

    Even IF this was a true innovation, how long would it be before the open source community has a better version running on *BSD/Linux?

  • why i need toString()? i want the shell to handle text and text only varibles.

  • Hmmmmmmm, let's see here...

    Ok, first, to all the Windows fanatics who've never even bothered to learn anything about *nixes, and to those who don't know enough: no, this isn't a bash clone. Python, on the other hand, let's you do all this and more. And all this talk about "I'm sure the open source community will have a better version running on *BSD/Linux by that time," THEY ALREADY DO, AND HAVE HAD, A BETTER VERSION. Why???

    Let's examine how this works under Windows, shall we?

    kernel, systems calls

    called by:

    win32 C API

    called by:

    ATL/COM to turn procedural code into a more object-oriented "design" (never mind the fact that all they're doing is putting an object-oriented wrapper around procedural code, ie, more overhead)

    called by:


    called by:


    Ok, so that's five layers.

    Now, let's examine how this is done under Python or bash (when OOP is not needed)

    kernel and api system calls

    called by:

    Python (or bash)

    need to connect to desktop applications? Running KDE?

    application api interface

    called by:


    called by:

    Python (or bash)

    2 layers for system call, 3 for desktop application control


    I wonder what could be better, call after call, objects constructed to hold objects it constructs to hold the variables it needs to in turn pass to the win32 api, which will then make calls into the kernel, if needed


    straight translation of the Python or bash commands into either direct api calls, or calls to DCOP, which in turns makes the requisite direct calls.

    Hmmmm, I bet it would take a genius to figure out:

    a) which one is going to be faster

    b) which one has more areas in which bugs can bring ever thing to a blue-screening, um, er, crashing halt

    c) tried and true, known to be reliable code which has been in use for many years, or a new creation by a company which is notorious for producing poor quality software, in part because the chief software architect doesn't happen to know his ass from a hole-in-the-ground about architecting good quality software, but thinks he does, or just plain doesn't care

    d) which design just plain makes much more sense, especially to one who knows how truthfully important it is to follow the saying, "Keep it simple, stupid!"

    damn, I wonder.

  • Really, this is HIPE as it's fullest.... Cmon yo guys you know better. This is a modified VB Script ... Compatibility with old .bat files anyone? Thank you. You can say Python can resemble such a shell too or Jython.

  • Can't stop laughing.... HAHAHAHAHHAHA

  • from /.

    timing sux

    MS power users want it NOW, not years from now

  • If they want CLI, they should use UNIX!

  • Yes, this "msh" stuff is pure hype. With the right references (say, ones for VB Script and Windows Scripting Host and one for writing NT command files), then it is close enough to a unix shell scripting environment, but of course, the example code initially posted looks just inherently stupid and unreadable.

    CMD.EXE is a far step beyond COMMAND.COM (remember, on NT-based systems COMMAND.COM is just a wrapper that runs CMD.EXE anyways...) that it is almost usable. WSH makes it even more usable, but still not up to even sh.

    At least it is pretty obvious to tell what is happening with a VBScript/WSH script file.

    MS hasn't done much with its command-line environment because it has tried to steer everyone completely away from it, yet those who know that this is not possible trog on slowly using the tools that MS has, use Cygwin or U/Win, or just use Linux or other Unix variant.

    MS should stop "innovating" sometimes and realize that the typical wheel, round and boring as it is, is about as efficient as it gets, and that there is no way they will make a square be able to work as good.

    It really remains to be seen whether it really is "evolutionary", even (which implies old stuff, with new stuff thrown in that just works better than the old stuff it supplants) than unix shells. I really doubt that it will be.

    "KISS" (keep it simple,, stupid) really means nothing at all at Microsoft, which seems to only know how to "innovate" for innovation's sake, much like a politician "does" stuff just to be able to say at election time, "look at all the things I did for you!".

    Sure, pipes and "everything is a file" are so 30-years-old technology, and with feature-rich stuff, more complex things can be done without having to do so much work around it, but the 90/10 rule of shell scripting is not to do complicated things that a "real" (i.e., C/C++/C#), but merely to automate simple steps that seem to occupy 90% of many people's thought and task spaces.

    And that simple reduction of "everything is a file" makes so much just inherently possible and doable in a Unix-based shell programatically...

    The Unix Way seems to meet this goal more than adequately, without pretending to be anything other than what it is.

    Somehow, after 15 or so years for me, the Unix Way just...still works.

  • Personally I have too often to run the Amiga emulator to do what the MS shell can't.

    And what does the article say ? "file aliases are possible" LOL :-)))))))))))))

    I do this for years now on my Amiga ! :-)

  • Let's see...

    1. Let's all slam MS for implimenting a feature that *NIX has had for years. So it's a good feature, but we don't like it if another OS agrees, and provides those features to it's users?

    2. Are you sure that your old shell had a native object model? Can your shell script enumerate all the properties on a dynamically instanciated object at run-time? I'm just asking, since I don't use sh/csh/ksh/bash/etc.

    3. Are there any real innovations that were not in another OS/Shell of the past? I get tired of people pointing out "They had that feature in Be/Amiga/..." So what. It is boring.

    4. I believe that MONAD is not an attempt to be more *NIX like, but rather, to provide a shell that is as powerful as any in the *NIX camp. I predict that there will be an object and a set of tools to facilitate migrating your *NIX scripts to MONAD. This is about removing a perceived advantage held by the *NIX crowd.

    5. This reminds of the days when they shipped a BASIC interpreter with their OS (GWBASIC). That gave the end users some power to write their own apps. I love it when the users are empowered.

  • Let's see...

    1. Let's all slam MS for implimenting a feature that *NIX has had for years. So it's a good feature, but we don't like it if another OS agrees, and provides those features to it's users?

    2. Are you sure that your old shell had a native object model? Can your shell script enumerate all the properties on a dynamically instanciated object at run-time? I'm just asking, since I don't use sh/csh/ksh/bash/etc.

    3. Are there any real innovations that were not in another OS/Shell of the past? I get tired of people pointing out "They had that feature in Be/Amiga/..." So what. It is boring.

    4. I believe that MONAD is not an attempt to be more *NIX like, but rather, to provide a shell that is as powerful as any in the *NIX camp. I predict that there will be an object and a set of tools to facilitate migrating your *NIX scripts to MONAD. This is about removing a perceived advantage held by the *NIX crowd.

    5. This reminds of the days when they shipped a BASIC interpreter with their OS (GWBASIC). That gave the end users some power to write their own apps. I love it when the users are empowered.

  • I probably dislike Microsoft a hell of a lot more than most of the people posting Here. I worked for them as a dev lead in a product group, and know first hand how they operate. That said, I must say the vast majority of the clowns posting in here are clueless jackasses. It's cool to hate Microsoft, but you fools make yourself look like nitwits with your ignorance.

    good day.

  • I'm working on putting together more info on this topic, and am still recovering a bit from jet-lag.

    Thanks for the powerpoint link, and I really enjoyed that session on Wednesday.

  • MONAD is utterly cool. Of all the presentations at PDC, this one most rocked me!!

    I see monad/msh as a mixture of the very best of scripting techniques (from the Unix World), mixed with Perl, and totally based on .NET. A developer and admin friendly uber-power tool.

    I want MSH NOW!!!!!

    MSH rocks

  • Finally. With aliases I can set ls to mean dir. I hate all M$'s awkward commands! dir? del? copy? Get real. bash is much more flexible and easy to understand. Ah: ls, rm, cp. Sound nicer, don't they? Less n00bey.

    I hate the command shell in Windows cause half the stuff that worked in DOS don't work in it. This better not be another piece of incompatible crap

  • You can do aliases already, sort of. Just create

    a little ls.bat file this:


    DIR %1

    Bingo. An ls command in Windows.

  • ok ok we all know its going to be incompatible, but hey, if you are so good at coding, then translate.

    If you like linux so much, then stay with it, and do not touch ms products (and viceversa).

    But please stop whining, if you know "that" much then code your own os and sell it... if you have a cool idea, patent it now and then develope it... enough with this "ms sux because doom wont run under its os".

  • hey its great,now micro$oft have understood the power is in SHELL

  • sfu - from what MS said at PDC, Monad just requries .NET Whidbey, so should be able to be released long before Longhorn.

  • What a MS-bashing magnet this post is.

    Too bad most Unix lovers are such whining idiots...

  • All this CLI stuff is wrong from the beginning.

    The CLI, to be useful, has to be lightweight, fast, and let you easily INTERCONNECT programs.

    Anything below or over that is just dumb. You would be better off either with a cool explorer window or a real programming language.

  • comment summary

    # of simple anti MS trolls: 46

    # of simple anti *nix trolls: 0

    # of people who needlessly point out that similar things have been done before: 26

    # of people who needlessly point out that it is needless to point out that similar things have been done before: 34

    # of people who think they are the first to make a joke using the word 'gonad': 6

  • Pax01: you miss the point here. For a start, the CLI gives you control that piping of text never could ever give you. You get type safety, easy extensibility, code access security and much, much more.

    The Unix guys were right over the basic concept. MS has just improved it.

    As for fast, on a Longhorn machine you'll have at least 1gb of ram, and a fast processor. With that sort of hardware, the CLI will be fast enough.

  • Want aliases? Use doskey.exe, which allows a /macrofile switch which does just what you'd think.

  • vasudeva: aliases are but a tiny part of monad. A tiny, tiny part.

  • Sounds promising. This could actually replace bash,

    reducing by one the number of reasons you need cygwin.

    That's a good thing. Plus, extra bonus points because

    it will ship with the OS OOTB, so you can rely on its

    being there.

    Of course, I quit writing scripts in bash a while

    ago when I learned Perl, but nevermind... Perl still

    for some reason doesn't ship with Windows OOTB. MS

    really needs to work up a deal with AS on that...

    but barring that, this still looks to be a great

    improvement over cmd.exe, to say nothing of the Win9x

    command prompt.

    Ummm, when is this going to be released, again?

  • > However, by the time Longhorn comes out (206? 2008?)

    > and is accepted by users at large, it is reasonable

    > to expect that the OSS community will have created

    > something comparable.

    Well, yeah, of course (we'll have Perl6 by then, for

    crying out loud) but that won't make it available on

    an out-of-the-box Windows system. This will. So it's

    a good thing.

  • > Let's all slam MS for implimenting a feature

    > that *NIX has had for years. So it's a good

    > feature, but we don't like it if another OS

    > agrees, and provides those features to it's users?

    I don't think they're so much slamming MS for wanting

    to implement this feature, as for failing to get

    around to it sooner. They're being needlessly

    confrontational about it, but it is surely true

    that this would have been useful in 1995.

    > 2. Are you sure that your old shell had a native

    > object model? Can your shell script enumerate all

    > the properties on a dynamically instanciated

    > object at run-time? I'm just asking, since I don't

    > use sh/csh/ksh/bash/etc.

    sh doesn't have that, and I don't think bash does

    either. The others I don't know. But Perl has it,

    ever since 5.003 or so, and Perl is more a part of

    most modern unices than the command prompt is a

    part of Windows. And by the time this comes out,

    we'll be vanishingly close to Perl6, which will have

    a much *better* object model (context-aware objects,

    among other things) that will make all this look

    obsolete. So yeah, the OSS community has this.

    That doesn't mean Windows shouldn't have it too,

    of course.

    > Are there any real innovations that were not

    > in another OS/Shell of the past?

    Probably, but...

    > I get tired of people pointing out "They had that

    > feature in Be/Amiga/..." So what. It is boring.

    Actually, ITS, back in the days of the PDP8, had

    a feature that I'm *still* waiting to see in a

    modern, desktop-oriented OS. VMS has it, but I

    don't want VMS on my desktop (go figure). I am of

    course talking about filesystem-level versioning.

    BSD doesn't have it; Linux doesn't have it; Hans

    Reiser hasn't implemented it; HFS+ (Mac FS) doesn't

    have it; FAT *certainly* doesn't have it, and NTFS

    doesn't have it either. It remains to be seen, but

    I am not holding my breath for it to be in WinFS,

    either. Shame; it's a *useful* feature.

    > I believe that MONAD is not an attempt to be more

    > *NIX like, but rather, to provide a shell that is

    > as powerful as any in the *NIX camp.

    Semantics. *nix has a more powerful commandline,

    Microsoft knows it, has known it for years, and now

    that they perceive Linux as a threat, they're finally

    ready to *do* something about it. So yeah, they're

    not copying bash per se, but what they are doing

    is to introduce a powerful feature to compensate

    for their previous lack. In that sense they are

    copying *nix, not in the sense of cloning, but more

    in the sense of taking inspiration from an idea.

    > I predict that there will be an object and a set

    > of tools to facilitate migrating your *NIX scripts

    > to MONAD.


    > This is about removing a perceived advantage held

    > by the *NIX crowd.

    Yes, absolutely. There are still some other pieces

    they'll need -- notably, a decent text editor -- but

    this is a start. And turnabout is fairplay, because

    the *nix crowd have been working hard on GUI toolkits

    to try to do exactly the same thing in reverse.

    > This reminds of the days when they shipped a

    > BASIC interpreter with their OS (GWBASIC). That

    > gave the end users some power to write their own

    > apps. I love it when the users are empowered.

    Agreed. Though today MS ought to be shipping Perl,

    at minimum. I'm sure they could work an agreement

    out with ActiveState if they wanted to. They're

    the only remaining major OS that doesn't ship with

    Perl, unless you count VMS, which is heading toward

    end-of-line status rapidly now.

  • >One last thing: anything can be mapped to a drive, and drives don't just have to be letters. (Ok, I lied - that was 2) The example I was shown was that the registry was mapped to a drive, and you could navigate it like any other drive, with the results being returned from the commandlet as .NET objects!

    Micro$oft had "invented" a new feature of MONAD;)

    This feature is very similar to AmigaDOS command "ASSIGN". This command was implemented in AmigaOS since 1987:))

    No more comments...

  • sometimes future mocrosoft says

    we have status discover of new command format

    just better new comand format use only software

    made by MS ;))

  • jonadab: freebsd 5 does not include perl, afaik (one surely can install it from ports, but it is not part of system anymore).

    to keep things on topic: msh may or may not be usable, based on its somplicity, not power. the good thing about unix tools is that they adhere to KISS principle - i can say

    $ find -name '*myfile*'

    otoh, 'file' is really sophisticated and powerful.

    If monad will lack simlicity - it will be yet another unused feature in windows.

  • Jonadab sez:

    > They're being needlessly

    confrontational about it, but it is surely true

    that this would have been useful in 1995.

    I take some issue with this statement. First, I did not get any sense of confrontation from the PDC persentations. It was straight technical: this is what is is, why it's cool and what you can do with it.

    Regarding 1995: heck, I had to try to teach Unix admins NT in 93! Man was that hard - they all were whining for their shell. :-)

    But rightly so. And yes - MS got it wrong, and CL scripting really is a better way to go about it. I think the guys concede this.

    What I like is that they've listened and done something -better- than just implement a Unix shell.

  • Are you too bussy with copying other OS-stuff that you just now reached the shell??

    Wow, I am waiting for the first Shell-Secure-Holes-Updates. May 19MB ;-))

  • if ms are going to do that, then they had above all BETTER finally allow windoze to operate effectively without any gui at all. I`m amazed by how rarely people seem to notice this severe deficiency. That could actually turn their gui-biased dog poo into a grown-up os.

  • pls get real : SHELL over GUI

    Shell is supposed to be used for quick and dirty things... i.e. fire a command, chain 3-4 commands on the pipe...

    if u want something more complex u have plenty of choices : bash, perl, python, ruby to name a few.. and then chain-together again ..

    Even if MS makes a some-sort-of-shell it still dont have the rest :

    grep, find, sed, awk, tab-completion and so on again to name a few.. (coping them from unices may help abit)

    U will never make object oriented program on the console, for this u just fire an editor (not Notepad) write what u want and then use it as a one additional command from the arsenal..

    So even if u get this MONAD today u will need a couple of years so that u find what are most useful commands needed get them written and accepted by the whole MS community, and then the hard part included by default from MS.

    So it would take a years-of-years to get the real power of shell under MS.

    Later under Windows we have another problem for the shell to be usefull it has to be slick and second MS has to make process-startup under Windows alot faster.. See under *nix u expect to fire many shell/perl/etc scripts one after another so the process-creation&startup is a way faster for than windows..

    MS has made a different route as design desicion make all-GUI and that is the reason they can't make monah a better CLI than what *nix have, which is ok 'cause they concentrated on GUI.

    On the other hand Linux may not get better GUI for some-ms-users which is ok too..

    What MS want to do with this toy is to attract potential sysadmins and such or stop the ms-ppl converting to unices.

    ? Believe me the users that use CLI know why they use it ?

    making shell for the sake of making shell or marketing purposes doesnt help the users..

    Dont get me wrong i would love see some better shell (available by default) under winboze even it is on the stage on which 4DOS was in the past..:")

    ooops forgot I'm not using windows, so i dont need shell under windows :")

  • So will MONAM come with a gui so I can point and click on stuff?

  • I was a unix developer for about 12 years. I have also been a windows developer since NT came out. Being familiar with both unix scripting and .NET programming, I can tell you that MONAD is completely different from any unix shell.

    Reading the slashdot posters here, it seems that most fall into one of two categories: post without reading, or post without understanding. This does not elevate the anti-MS "community". On the contrary, the "community" becomes subject to ridicule, and it is difficult to see the difference between the "community" and a lynch mob.

    If you wish to post in a technical forum, at least try to understand what you are commenting on. This shell is a very big deal. The main reason is its integration with .NET. If you don't understand that, maybe you should learn a little about .NET before posting.

  • *nix vs ms?

    If the *nix whingers stopped whining, they might actually move their technology past where it was 20 years ago.

    Let me see if I get this right - Linux/BSD is free and you still can't get people to use it?

  • MSH Moves on.

    MS has made a new drop of MSH available to testers. Some big language changes (as to be expected) but some GREAT thinking. I've put some stuff up on my blog if anyone's interested!

  • Thomas,

    I've been very quiet on this subject due to the beta NDA. Wish I could post more about the new features, but there's not a public source of info about the new build that I could have learned from out of NDA, so for now I can only post on bits I have seen during the PDC demos.

  • will this put all the Unix pipe | fans on the defensive?

  • OK.

    Name says it all.

    I hear you *nix Losers trolling MS for not doing it this way or doing ot that way.

    MS has more marketshare than *nixes and how can that be since they had a head start and evrything tends to grow exponentially...

    Ever wonder why...

    Superior marketing and giving it to the consumer "their way". Read into it as you like.

    Hell, this new shell may turn a few more of the "Daemons" to see the light...

    10+ years of Linux and the like and they still don't quite own the market despite the trade rags saying in 97' they were now on a competitive level in the market.

    Maybe in another 10...

    Keep trying...

    Wake up people.

    MS has done more to educate the masses than any goon in the clergy of *nix ever did.

    Or did you forget those dark and unwieldy days when the blind led the blind and no those of the Unix Church didn't think much of security either, it wasn't a concern...

    Cuckoo's Nest by Clifford Stoll sparked an interest.

    Clue: Mitnick's been FREED...


    Get over it...

    Each OS has its advantages...

    Take them as you will.

  • I just started writing about Monad too. Amazing stuff.

  • This is awesome. This is the only thing that I have really missed, and continue to really miss, in Windows. With this, I will be able to really do things that I would do with small shell scripts in Linux. This is GREAT! I can't wait to install it...


  • After reading most of the comments including the flaming about msh (monad) its quite obvious a number of people a willing to make comments whether against or for this without clear knowledge of what Monad actually is or does.

    Personally, I think Monad is potentially a very positive step for m$. Yes it is vastly behind in relation to the unix equivilent shells but it is finally here.

    The major positive note about Monad is that it attempts to introduce a standard for command line interface to most aspects of the M$ environment. Where as before one had to write a vbscript to do some things, batch for others etc etc, with Monad, the user potentially has the capability to use one method to access components such as Exchange, Active Directory, File Systems, IIS, Registry, .NET Components etc which (ignoring the security aspect) can only be a positive thing. The main flaw is integration of third party components, but as SDKs and plugins become available this flaw too will be removed.

    In reply to the unix v microsoft flaming, yes the unix shells have been around for much longer but are they really that much better? My experience of unix from Open Unix, AIX, Unixware, Solaris, Linux, BSD etc has been that problems exist with all shells. The main problem with Unix is the issue of having to manually bolt together components; no matter what one says about Microsoft, they do (now, not in the past) provide a capability to bolt components together (WMI/Monad/etc) and Monad providing a standard interface for this is very positive.

    In terms of Security, I believe Obscurity is not the best form of Security. If host and network based security defense measures are implemented correctly this should not be a problem. In terms of application bugs, these exist with both M$ and Unix applications and if an intruder is determined, im sure that they will achieve their goal.

    My view is if one believes that there are problems with any aspect, why dont they attempt to do better themselves. If they don't have the capability to do this, why not provide comments to vendors so that they can possibly include improvements rather than flaming randomly across forums. Yes there is no definitive resource to do this currently but i'm sure if enough people have the same attitude and vision, one will be created in the future.

    Cheers, Andy.

  • What I find interesting, is all the new innovations of Microsoft are things that been done in the past on other OSs. Sure, MS numnuts might gloat about how new is their implementation but what use is it for accomplishing real work quickly. Back in the days of OS/2 3.0, I wrote REXX command scripts that executed other command scripts on parallel treads with interprocesss communication through pipes. Something you cannot do easily even with Windows XP. Maybe they achive it with Longhorn, I don't know; but it will not be "new". You cannot even claim objects as being new, since REXX Objects were around since OS/2 4.0. I do agree that OS/2 is finally showing its age now, yet it still can tie up windows for such an old gunslinger. Infact on any Windows computer I use, I always install Regina REXX while its not as good as the native REXX of OS/2 its a far cry better and easier to use than Windows batch and WSH, especially since what I usually need is not a fancy interface to the GUI. I much prefer better data processing.

  • [href=// title="wangzhidaquang"]

    [href=// title="jingpingwangzhi"]

    [href=// title="mianfeidianying"]

    [href=// title="dianyingxiazai"]

    [href=// title="MP3 free download"]

    [href=// title="diannaoaihaozhe"]

    [href=// title="duangxingcaixingxiazha"]

    [href=// title="dianyingxiazai"]

    [href=// title="yinyuexiazai"]

  • I been programming with MS since windows 2.0, I been defending them all these years, but I have given up using windows! There is so much more flexibility and simplicity with unix.

    I now use Linux for cheap web/office servers, and Mac OS X for my desktop and laptops.

    For goodness sake microsoft, just release a unix core version of your OS, or you will loose more developers like me.

    I have developed for .Net for a few years now, and MFC before that, etc. Even though I liked .Net and C#, that was not enough to hold me on the platform. I dont think another microsoft-only NEW command line scripting language would really help me.

  • so they've ported the bash shell - who cares - most windows users cannot type anyway.

    what they need is a more graphical command line - perhaps one where you could run programs by dropping icons on the prompt or using a wizard/gui to paste the command text into the shell.

    it would be really cool if the command prompt had a user-selectable background wallpaper - that would really help usability.

  • Monad is quite the tool... It will be nice to have a unix equiv. or better with all the power of .NET.

  • This informations are very useful
    Thanks a lot...

    King Regards!

Comments have been disabled for this content.