Slashdot Mirror


Should The Next Windows Be Built On Linux?

scrm writes "The next version of Windows should be built on top of Linux, according to this article by Robert Cringely of PBS." If Microsoft wanted to, they could be the world's largest vendor of Free software .. couldn't they?

119 of 763 comments (clear)

  1. And compromise compatibility with drivers, etc by Uksi · · Score: 3, Insightful

    I'm sure that a lot of Windows driver developers will enjoy porting their drivers over to the Linux architecture.

    1. Re:And compromise compatibility with drivers, etc by perotbot · · Score: 2, Funny

      You mean we'll finally get winmodem drivers for linux??? whooo hoooooooo! I can use by thinkpad!

      --
      ~corporate tool, but employed~
    2. Re:And compromise compatibility with drivers, etc by GrenDel+Fuego · · Score: 3, Informative

      They already exist. Not for every modem, but a number of more common ones.

      IBM even provides links to some of the drivers I believe.

    3. Re:And compromise compatibility with drivers, etc by miu · · Score: 5, Insightful
      Have you read this dope's article? I'm begining to wonder if he even knows what a computer is much less an operating system. There are so many holes/problems with this guys article and way of thinking that I don't even know where to begin. I mean damn!

      Yeah, Cringely is either incompetent or trolling for readers. A couple of glaring errors are worth pointing out:

      Even today, you can still get to a C: prompt under Windows XP, which means a disk operating system is hiding there no matter what Microsoft wants us to believe.
      Wrong. cmd.exe != DOS
      Windows XP is not an operating system. It is a windowing system that sits atop an operating system much as KDE or Gnome sit atop Linux.
      Wrong again. explorer.exe != Windows
      Now back to Microsoft putting Windows on top of Linux. Linux is better, faster, stronger than whatever is living underneath XP now, right? Performance would improve. As Mike Class points out, by not having to develop its own OS, Microsoft could also save money. They wouldn't need however many people are presently devoted to maintaining the underlying OS that isn't supposed to be there.
      Strike three! There are lots of things to like like about Linux, but these claims are ridiculous.
      --

      [Set Cain on fire and steal his lute.]
    4. Re:And compromise compatibility with drivers, etc by LostCluster · · Score: 4, Informative

      The C:\ prompt within a window has always been an illusionairy thing. Think about this for a second...

      In Windows 3.1 you could run DOS-atop-Windows-atop-DOS... but if you ever tried to run "Win" in that environment, you would get a message that indicated that Windows-atop-DOS-atop-Windows-atop-DOS just wan't going to happen, you're not at a "real" DOS prompt. You didn't have a full-featured version of DOS there, just the interface level.

      If you carry that forward to XP, the "DOS" in XP doesn't directly control the low-level stuff anymore. Some nameless, faceless part of Windows does.

      DOS-within-Windows is now just an alturnate wacky skin for Windows Explorer. It's just a familiar text-based way to do things, not a low level OS anymore.

    5. Re:And compromise compatibility with drivers, etc by EvilNTUser · · Score: 4, Interesting

      "Yeah, Cringely is either incompetent or trolling for readers."

      Yes he is, but he's just one person. What really saddens me is how pervasive this kind of thinking is. People who genuinely believe XP is based on DOS are a real threat to getting intelligent users to migrate.

      When I was younger, I was originally turned off by the Mac platform because of all the ignorant users. It wasn't uncommon to hear them condescendingly say that Windows is based on DOS and Macs do true multitasking etc. And there I was, sitting in front of a box running a *preemptively* multitasking kernel (NT 4.0 at the time), thinking "there's no way I want to associate myself with these retards".

      When I grew up, I realized how stupid I'd been and acknowledged that I didn't really hate Macs, but their users. Today I might even consider buying one because of OSX, but my earlier feelings show just how much a platform can be hurt by bigoted users.

      --
      My Sig: SEGV
    6. Re:And compromise compatibility with drivers, etc by miu · · Score: 2, Informative
      but rather the NT Kernel, which could easily be consider like the DOS kernel, but built more sturdy.

      DOS was pretty much a driver loader built for a real mode cpu. NT is a modern OS. That means:

      • Virtual Memory
      • Protected mode
      • Task Scheduling
      • A filesystem manager
      There is another huge difference is the size of the NT kernel vs. DOS. NT is built "more sturdy" because it would colapse under its own weight if it were not.

      Windows 3.0 had more features of a modern OS than DOS did. It used DOS pretty much the way DOS used the BIOS, bootstrap with it and then shove it into the background.

      --

      [Set Cain on fire and steal his lute.]
    7. Re:And compromise compatibility with drivers, etc by miu · · Score: 2, Insightful
      Well, DOS would keep running if I ripped the BIOS chips from my XT, IIRC.

      Not quite, because DOS itself sometimes used the BIOS services, it just added a "system call" interface over them.

      So, if I were to overwrite the memory DOS had loaded itself into with random info after windows 3.0 had loaded, would it have kept running happily?

      No. Windows 3.0 used plenty of DOS services. Not least of which were real mode device drivers, but also INT 21h.

      Although Windows 3.0 was not an OS ("thing on a thing" was the most common title I remember), it was closer to the CS definition of an OS than DOS.

      --

      [Set Cain on fire and steal his lute.]
    8. Re:And compromise compatibility with drivers, etc by spongman · · Score: 2, Interesting
      The idea that NT is OS/2 is complete myth. Sure some of the user-mode API names are similar (mostly because they're similar to their common Win16 ancestors - for ease of application porting) but the underlying kernel architecture is completely different.

    9. Re:And compromise compatibility with drivers, etc by Anonymous Coward · · Score: 5, Informative

      In Windows 3.1 you could run DOS-atop-Windows-atop-DOS... but if you ever tried to run "Win" in that environment, you would get a message that indicated that Windows-atop-DOS-atop-Windows-atop-DOS just wan't going to happen, you're not at a "real" DOS prompt. You didn't have a full-featured version of DOS there, just the interface level.

      Actually, it was the "full-featured version of DOS" running in that DOS prompt under Win3.1 and Win9X.

      The X86 architecture has 2 main modes of operation: real mode (compatibility with 8086/186 processors -- all PCs to this day boot in this mode) and protected mode.

      Under protected mode, it was possible to create something called a Virtual 8086-mode task. This allowed for real mode simulation within a protected mode environment, thus allowing real mode programs to work.

      Each V86 session can, for most practical purposes, be made to think it is the only thing running (with no knowledge that it is being virtualized and having various instructions, operations, and interrupts intercepted by the protected mode operating system.)

      Getting into protected mode from V86 mode is not possible, hence why Windows wouldn't run in a DOS box. It is also possible for real mode programs running in V86 mode to detect V86 mode by checking the appropriate processor status flag (I'm not sure if the OS can intercept this.)

      DPMI (DOS Protected Mode Interface) is what eventually allowed 32-bit DOS programs to run in true real mode or in DOS boxes. In DOS boxes, Windows would be the DPMI server; but in real mode, you'd need an external program to get you into protected mode first -- CWSDPMI, for example.

    10. Re:And compromise compatibility with drivers, etc by buswolley · · Score: 2, Funny

      Microsoft M$ has so much cash on hand they could:
      1)decide they are going to sell refrigerators
      2)spend ten years in refrigerator R&D
      3)flood the refrigerator market
      4)still have cash
      5)profit lol

      so. Linux? no problem.
      this question should have no relation to the relation between programming for windows and Linux etc. it is purely about how rich they are.

      --

      A Good Troll is better than a Bad Human.

    11. Re:And compromise compatibility with drivers, etc by runderwo · · Score: 2, Insightful

      Why are the other clueless idiots getting modded up, and this post with correct and informative content gets left at +0?

    12. Re:And compromise compatibility with drivers, etc by squiggleslash · · Score: 3, Interesting
      The idea that NT is OS/2 is complete myth.
      It's not a myth, but it's a misleading fact that is doubly misleading because there's an OS/2 subsystem in NT that people use as evidence that it's based on the same code as the OS that was marketed as OS/2.

      NT, as a project, started out as "OS/2 version 3". Microsoft and IBM worked together on OS/2 version 1, and planned to split their resources so that IBM would create a version two, that was fully thirty two bit (wouldn't run on the much maligned 80286 and so wouldn't need the kinds of grafts and fixes running on that chip required), and Microsoft would concentrate on producing version three, a complete rewrite that would make use of the latest ideas in operating system design, be secure, genuinely multiuser, run on non-Intel architectures, etc.

      When IBM and Microsoft had their spat, the projects continued, but without Microsoft seeing any need to make the "next generation" OS have anything to do with OS/2 at all. Compatability requirements were dropped to just the command line environment, the operating system was renamed (choose your own favourate urban legend, and about the only real sign that the operating systems were related was that the very first version, 3.1 (yeah, 3.1 - I could be cynical and suggest it's because Microsoft figured they never got anything decent out the door until "version 3" so they might as well jump the line... but I believe the real reason was that they wanted the version numbers to match those of the DOS/Windows line, NT had a Windows 3.1 compatable subsystem after all) could optionally be installed on an HPFS partition - HPFS being the OS/2 file system. This feature was dropped from later versions (I'm trying to remember that far back, but I think one issue was that NTFS wasn't implemented until 3.5 or 3.51 or something. Can anyone help me here?)

      Unfortunately, this story has been misunderstood by a lot of people to mean "NT is just a version of OS/2". It isn't. It owes its history to OS/2, and maybe if OS/2 hadn't happened, Microsoft would be migrating its customers to "Xenix Windows". But that doesn't make it the same code and it isn't.

      --
      You are not alone. This is not normal. None of this is normal.
  2. Yeah right by KilljoyAZ · · Score: 5, Funny

    That's about as likely as Jack Valenti saying, "We actually don't need copyrights to last this long," or Duke Nukem Forever being released.

    --
    This .sig is currently on hiatus for retooling.
    1. Re:Yeah right by xingix · · Score: 2, Funny

      And capatlistic tendencies are bad? God forbid anyone try and make money.

      --

      Confucious says: Man who runs behind car gets exhausted.

      // jeku.com

    2. Re:Yeah right by Tsian · · Score: 3, Insightful

      And capatlistic tendencies are bad?

      No, but then again, its not like we have (or want) pure capitalism. Pure capitalism would be NO government aid. No major tax cuts, no negative net taxes paid back to corporations. No corporations being handed publically funded projects (aka the phone lines, the railways etc).

      Today's capitalist system thrives because of the socialist controls imposed on it...

      Afterall, who needs the FDIC anyway?

    3. Re:Yeah right by apweiler · · Score: 2

      Because without the government, we all become heartless bastards who don't give a damn about our neighbors. Just like without religion and the fear of eternal damnation, we all would turn into homocidal maniacs.

      Actually, yes, for the first part. 'Neighbours'? The general tendency as far as I can tell is that poor people and rich people tend to live in different neighbourhoods. And so you think my $10k-a-year neighbours would pay for my kid's $50k cancer therapy? And even if they did, I'd rather have a government-administered welfare system that I can *depend* on if I'm in trouble rather than having to hope for my neighbours' charity.

      Anyway, an interesting thought crept into my brain here:
      Half-asses deregulation will always be a failure

      Some people I know and have been around a fair bit recently are active in the anti-neoliberalism movement or whatever you want to call it, FWIW the far-left area of the spectrum. Some of those actually lean toward anarchism, obviously not in the sense of chaos and destruction, but in the sense of building a society where everyone will get along without any government. (While this sounds nice, my optimism about it being possible is rather limited.) The interesting bit is: Isn't that exactly the same thing that a) communism was originally about, and b) that radical capitalists like you are proposing - if the government keeps out of things (deregulation etc.) (and eventually, hopefully, disappears) people will just get along and everyone will be happy. I'm not saying your idea is bad, though I doubt it can work; what I want to point out is that this is really where right and left meet (well, certain types of right & left - not the anti-abortion anti-drug hard-line religious right, and not the Stalinist/IngSoc 'left', obviously). Something to think about, innit?

  3. No. by tshak · · Score: 4, Interesting

    No, but it should be built on a BSDish *nix ala OS X. Heck, MS could even use Darwin - wouldn't that be an interesting turn of events!

    --

    There is no longer anything that can be done with computers that is nontrivial and clearly legal. -- Paul Phillips
    1. Re:No. by CptNoSkill · · Score: 5, Funny

      Yea Microsoft would never base their products on something that apple made.. oh.. wait a minute....

  4. They'll use FreeBSD or NetBSD if anything by m0nkyman · · Score: 4, Interesting

    GPL licensing is anathema to them, but they seem to enjoy using BSD licensing....

    --
    ~ a low user id is no indication I have a clue what I'm talking about.
    1. Re:They'll use FreeBSD or NetBSD if anything by BandwidthHog · · Score: 4, Insightful

      GPL licensing is anathema to them, but they seem to enjoy using BSD licensing....

      But only in the one direction, no? Do they ever license their own work as BSD?

      --

      Quantum materiae materietur marmota monax si marmota monax materiam possit materiari?
    2. Re:They'll use FreeBSD or NetBSD if anything by robbyjo · · Score: 3, Insightful

      IMHO, considering what Microsoft has done in the past, the right word here is not "use", but "cannibalize".

      --

      --
      Error 500: Internal sig error
    3. Re:They'll use FreeBSD or NetBSD if anything by sl3xd · · Score: 5, Insightful

      Of course they don't. That's why they like the BSD licence (and hate GPL): With the BSD licence, they can take all they want, have some obscure reference to the original authors in the documentation, and re-sell the work as if it were their own. The BSD licence doesn't ask anything more than to give credit where credit is due-- it's worth noting, however, that Microsoft has even violated that licence in the past. (They ripped off some fairly large chunks of BSD code, and never gave credit to the original authors).

      However, the GPL licence: It requires that Microsoft give back; the thing to remember is that Microsoft is like a roach motel for source code -- it checks in, but it doesn't check out. The GPL would require Microsoft to make available any code they change under the GPL; it takes away their absolute control over the code, and takes away their ability to (over)charge for said code. Plus, a good roach motel doesn't let anything escape.

      --
      -- Sometimes you have to turn the lights off in order to see.
    4. Re:They'll use FreeBSD or NetBSD if anything by Ctrl-Z · · Score: 2, Funny

      However, the GPL licence: It requires that Microsoft give back; the thing to remember is that Microsoft is like a roach motel for source code -- it checks in, but it doesn't check out.


      Sorry, I hate to be picky, but don't you mean that Microsoft checks code out but it doesn't check in?
      --
      www.timcoleman.com is a total waste of your time. Never go there.
    5. Re:They'll use FreeBSD or NetBSD if anything by Elwood+P+Dowd · · Score: 2, Interesting

      Um. The BSD license *used* to require credit. Depending on what BSD license the original project used, a copyright notice may or may not have been required. I'm sure you wouldn't just say that because you couldn't find the copyright notice, so it's still entirely possible that MS did something wrong. I'll just need more to convince me. They've got a lot of well paid people that try to limit their liability, so...

      --

      There are no trails. There are no trees out here.
    6. Re:They'll use FreeBSD or NetBSD if anything by toxcspdrmn · · Score: 3, Funny

      That's because the misread it as the BSoD licence and thought it fitted their products perfectly.

      --
      "E pur si muove!" - attributed to Galileo Galilei, 1564-1642
    7. Re:They'll use FreeBSD or NetBSD if anything by Anonymous Coward · · Score: 3, Informative

      No, all versions of the BSD license require that credit is given to the copyright holder. You might be thinking of the advertising clause in older versions of the BSD license that required that the phrase "this product includes software written by [name of copyright holder]". That clause was removed from the BSD code by Berkeley some time ago.

      If you want to see some examples of the BSD license "in action" so to speak, see Microsoft's release notes for Windows XP. There credit is given to a lot of people who have released BSD licensed software; not only to Berkeley, but also to people like Luigi Rizzo who have done a lot of work on the FreeBSD kernel.

    8. Re:They'll use FreeBSD or NetBSD if anything by jez9999 · · Score: 2, Informative

      Lol.

      (at the bottom of relnotes):
      "Portions of this software are based in part on the work of Luigi Rizzo. Because Microsoft has included the Luigi Rizzo software in this product, Microsoft is required to include the following text that accompanied such software:"

      After all that, is it really worth having your credit given at all? How about requiring that the user have a good chance to see it, instead? So they have to put it in bold on the desktop or something. :-)

  5. wait..... by skinnedmink · · Score: 5, Funny

    If anyone could ruin the stability of Linux.....it would be Microsoft.

    --
    peace be with you.
    1. Re:wait..... by zcat_NZ · · Score: 2, Funny

      Linux stability doesn't need ruining. the plethora of shit that comes with your average distribution does more than a good enough job.

      so don't run redhat then.. sheesh!

      --
      455fe10422ca29c4933f95052b792ab2
    2. Re:wait..... by jjeff · · Score: 2, Insightful
      I crash linux 20-30 times an hour doing simple stuff - why do people continue to feel linux is stable?


      You are so full of shit - you would have to be using a machine which takes less than 1 minute to boot.
      What the hell are you doing to cause this?
      I use my desktop/personal web/mail server for any number of things such as browsing the web with a number of different browsers, playing games both with wine and native linux ones (using supposedly "unstable" nvidia drivers - they have always worked great for me) and I havent had a crash for months. In fact the only time its been rebooted was when my fiancee's brother came to stay and couldnt sleep with the computer fan going.

      I dont know why you people spout such crap.

      --
      when everything is working perfectly.. BREAK SOMETHING before something else FUCKS up!
    3. Re:wait..... by JW+Troll · · Score: 2, Interesting

      he's referring to the crappy applications that run on top of Linux, obviously. I've experienced the same thing and it pisses me off. Every three months I try the latest Red Hat, Mandrake, and Lycoris.
      Yes, I'm a geek with waaaay too much time on my hands, but I shouldn't be beta testing applications that are marked stable for crying out loud. KDE should be labelled "alpha 0.3.1" by commercial standards.

      --
      just like the humble blood clot... turboporsche@telus.net
  6. Well.... by captainclever · · Score: 2, Interesting

    Well if i was calling the shots i'd set MS developers to write an alternative to X, perhaps in opengl or directx, that had all the same interfaces as QT and GTK and Motif so existing apps could be recompiled. A really fast graphical subsystem (instead of X) running on a Linux base, would make for an excellent and powerful platform, suitable for games aswell as general work.

    --
    Last.fm - join the social music revolution
  7. It's time to be realistic by scyta1e · · Score: 2, Insightful

    Let's be realistic now, Windows and Linux do different things. If you want actual control over your computer and a nice development environment, use Linux. If you want to access any kind of file type or hardware simply and easily, you're gonna use Windows. Sure one could be brought to perform like the other, but that would take a damn long time.

  8. The question is by Anonymous Coward · · Score: 5, Funny

    Will Linus accept the BSOD patch for the kernel?

  9. But no backwards compatiblity by shoppa · · Score: 2, Interesting

    The reason that "new" Windows releases still have a MS-DOS command line is backwards compatiblity. (And force of habit, by now.) Linux doesn't automatically offer that advantage (though the DOS emulators that run under Linux were useful to me in the mid-90's, and I'm sure they still exist now.)

  10. Pardon? by Acidic_Diarrhea · · Score: 5, Interesting
    "Now back to Microsoft putting Windows on top of Linux. Linux is better, faster, stronger than whatever is living underneath XP now, right?"
    This article posed an interesting proposition but in order for the whole premise to fly, this snippet really has to be a "Well, duh" type of question. I really don't know that it is. Without any definitive proof of this, the author is merely picking at straws. How does anyone know where the clunkiness of Windows comes from? I mean, the NT kernel isn't exactly a slouch and I'm not sure that Linux is vastly superior. How are we to know that the windowing system isn't the problem? Perhaps the real Operating System-type services provided by the kernel are faster and more powerful than the ones provided by Linux. We just don't know because a separation of the windowing system from the real OS isn't possible with MS's closed source system. Thus, this argument isn't really credible to make. It's an interesting hypothesis but there's nothing solid to say, "Yes! You're right!" There's really no way to know which underlying OS services are better provided by XP or Linux.
    --
    I hate liberals. If you are a liberal, do not reply.
    1. Re:Pardon? by wideBlueSkies · · Score: 2, Interesting

      >>We just don't know because a separation of the windowing system from the real OS isn't possible with MS's closed source system.

      I'll wager that the guys in Redmond have the Windows Kernel running on machines without the windowing system/fluff. They're not stupid people over there. There's no way that they could accurately benchmark kernel performance with all that crap running on top of it.

      I'll bet that they even develop the kernel seperately from the windowing system. They probably only test the 2 components together after a round of kernel changes, and standalone stability has been acheived.

      Even if the above isn't true, you know that somewhere in Redmond, some developer or group has got to have the Windows Kernel running standalone on a machine.

      Also, MS would be stupid to not benchmark their product's performance against the 'competition': LINUX and BSD. The only way to do so is with the raw kernel. At least it's the start of a good test.

      Would any MS developers like to comment?

      --
      Huh?
    2. Re:Pardon? by drinkypoo · · Score: 2, Interesting
      Not only that, but NT is a mostly microkernel-based OS. Right now it is targeted at the Windows NT HAL which does basically nothing but hardware access. Object management (Windows, devices, drivers, files, mutexes, processes, and threads, etc) is done entirely within the kernel. Perhaps some of that should be done by the microkernel. Mach, for example, manages hardware, memory, and threads; Windows currently manages threads.

      If it made sense for NT to use ANYTHING under it, it would make the most sense to stick with the NT kernel but target mach instead of the HAL, and move process/memory handling out of the kernel, allowing mach to manage these things. This is probably how linux should have been designed but as we know the microkernel/macrokernel debate has raged hotly since time immemorial and will not likely be finished any time soon. I do think it makes the most sense though, as it facilitates everything running in user space.

      Also I would not bother to port to any microkernel which does not support realtime scheduling (as does RTMach, but not normal Mach apparently) as you want to be able to use the same microkernel across all platforms, and microsoft has an embedded NT product. If you're going to move threading out of the kernel it has to do everything you've ever dreamed of. I guess they could add it to rtlinux if they hired a bunch of developers away from QNX or something :)

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:Pardon? by Anonymous Coward · · Score: 2, Informative

      Actually if you would like to see the Windows XP kernel running without the gui simply boot off of a Windows XP CD... or better yet, boot using a Windows Preinstallation Environment CD. Those are the CD's used by the tier-1 manufacturers.

      The Windows Preinstallation Environment boots up into a graphical interface but it only gives you a command window to use.

      If you think about it, trying to determine if your just using a kernel as opposed to a graphical interface is pointless. It is not like you can actually "see" the kernel. The kernel merely controls the rest of the OS and responds to commands that are given to it. Even different distributions of Linux show different graphical items and pictures while booting the kernel. It's not just a clear-cut thing.

  11. Erm no. More like bankruptcy. by Anonvmous+Coward · · Score: 2, Insightful

    "If Microsoft wanted to, they could be the world's largest vendor of Free software .. couldn't they? "

    They'd also be the largest vendor of Free Software filing for bankruptcy.

    I don't intend that comment as a troll. I know some investors. (My uncle is one...) I've talked with them about MS etc and what they like/dislike about them. If they were invested in MS, they'd be upset about MS giving their moneymaker stuff away. They'd likely sell their stock in a heartbeat unless MS put one hell of a spin on it. There's the whole matter of how you make free software profitable. They want return on investment. They want what's tried and true.

    Now, as for MS porting Windows to Linux: Wouldn't everybody (at least on /.) get their panties in a bunch accusing MS of over-extending their monopoly into the Linux world?

  12. Erm. The "sitting atop" could be questionable. by Elwood+P+Dowd · · Score: 3, Interesting

    Cringly seems to misunderstand something...

    Apple released Darwin under the APSL out of the goodness of their hearts (and their PR department, I'm sure). They don't have any restriction against using Darwin source inside their closed source components, like Aqua. I think this means that there are certain kinds of linking that you're allowed to do with BSD code that you aren't allowed to do with GPL code, if you're going to keep your IP proprietary. So Apple may not have been able to do what they did had they used the Linux kernel. For example, wasn't there a recent flap over Linus changing the name of some kind of trap to GPL_ONLY?

    I guess Microsoft could make this ok by GPLing anything that linked in that manner to the kernel, but it's definitely something that would have to be a consideration were this ever to occur.

    Ooooh. This would be an excellent way for them to embrace and extend, wouldn't it? Couldn't they release a Linux variant that was practically useless without their proprietary components? They wouldn't have to do that at first, but they might be able to work up to it...

    Iduno. Just talking.

    --

    There are no trails. There are no trees out here.
  13. One More Time by CajunArson · · Score: 5, Insightful

    Since this article was already highlighted on OSnews and Newsforge, I am once again forced to repeat myself:
    Cringely has no idea wtf he is talking about.
    Windows XP is NOT a simple windows manager sitting atop MS-DOS.
    But it has a DOS prompt!! Yeah, so does Linux if you install an emulator, does that mean Linux runs on MS-DOS?? The DOS prompt in XP is just another program that happens to look like what you used in the 80's before there was Linux :)
    I could go on and on about how XP is based off the NT core which came from VMS and how different the X server is from how MS does its graphical shell, but I'm sure many other posters will put up the same info.
    OK: Even ignoring why Cringely was completely wrong from a technical standpoint, here's why he's still wrong even if he were right (does that make sense?)
    MS: Has spent a boatload of money copying and building there own versions of what everyone else already had. They are finally starting to get it right, and are making money hand over fist doing it (at least in the OS sphere which is what we are talking about). Moving to a Linux base would be a HUGE investment, and MS software would go back to the stability of Win98 for 3 generations as they worked out all the bugs. As much as the Linux gurus on Slashdot would love to see MS sabotage themselves like that, they aren't that stupid.
    Linux: Linux would NOT be helped by having MS grab the Linux kernel and use it as a base for their OS. I also don't give a fsck what you'll say about "but the GPL!!" If MS were to do this they would withouth question weasal around the GPL or hire an army of lawyers to get it thrown out or watered down to the point it wouldn't matter. Meanwhile, they would either not give any code back to the kernel, or more likely would inject code specifically designed to slowly build up an IP claim over the entire kernel.
    MS doesn't like Linux but believe me, they are doing it a major favor by not trying to subvert it, and despite how much everyone here loves to bash MS, a whole bunch of the software running on
    Linux owes some credit to MS for providing a model to follow, like it or not.
    Once again, Cringely is proved to be a whole bag of hot air.

    --
    AntiFA: An abbreviation for Anti First Amendment.
    1. Re:One More Time by sl3xd · · Score: 3, Insightful

      MS: Has spent a boatload of money copying and building there own versions of what everyone else already had. They are finally starting to get it right, and are making money hand over fist doing it (at least in the OS sphere which is what we are talking about). Moving to a Linux base would be a HUGE investment, and MS software would go back to the stability of Win98 for 3 generations as they worked out all the bugs. As much as the Linux gurus on Slashdot would love to see MS sabotage themselves like that, they aren't that stupid.

      Of course, the actual logic of spending this money to build their own version of what everyone else already had is the troublesome part; There are major parts of the OS that have been quite literally 'carbon copied' from the Free/Open/Net BSD code, with a zero licence cost of any kind at all. Why they go about re-inventing the wheel when somebody is giving away a far better wheel (Such as the process scheduler, VM, file system, and network stack, to name a few) 'no strings attatched*', is beyond me... however it does reek of the NIH (Not Invented Here) syndrome. Of course that may not be the case, but Microsoft's apparent refusal to adopt larger portions of the BSD code seems like a bad business decision to me. There is just a lot less money that would have to have been spent, and the end result would have been a more flexible, stable, and secure system than what Microsoft developed in-house, and yet they get to keep all of the BSD-licenced code as tightly-controlled as the Windows source currently is. It seems like Microsoft shot themselves in the foot by not taking advantage of what amounts to thousands of man-hours of free (non-cost, no-strings attatched) work and research; passing up a free lunch is a very un-Microsoft like behavior.

      And I agree that it's crap to say that they would build the OS on top of Linux. Some people may idolize the GPL, and that's fine. Many feel the BSD licence is a more 'free' licence, again that's fine. Given the choice between the two, however, and Microsoft would almost certainly choose the 'no strings attached*' BSD code.

      *No strings attached meaning that there is zero cost to licence the code, and there are no terms on redistribution other than to give credit to the original authors; The GPL stipulates that any changes of the code must be redistributed, the BSD licence does not. This modified code redistribution is the disinguishing feature of the GPL to which Microsoft objects-- they do not wish to allow anyone access to their code (not without working out some scheme whereby Microsoft will recieve monetary 'compensation' for access to their modifications, at a minimum.)

      --
      -- Sometimes you have to turn the lights off in order to see.
  14. Nice idea, but... by kruetz · · Score: 3, Interesting

    Okay, this would be nice if Microsoft was purely interested in developing a great consumer OS. Unfortunately, they're not. They are only interested in their bottom line (hey, this is capitalism!). To this end, they want to remain a monopoly and have their software on everyone's computer. Which is fair enough.

    There are several problems stopping MS from using Linux:

    1) They have .NET server (which will Win2004 or something, now), all of their .NET software, LongHorn and the next SQL Server under heavy development. I'm sure they'd rather continue working on software they know will rake in billions of dollars than start from scratch writing a UI for Linux.

    2) Remember all the FUD about the GPL and Linux? Well, Microsoft probably doesn't feel like doing a three-point-turn and adopting Linux and proclaiming it as the underlying foundation to Windows. And I doubt they'll use Linux and just remain silent about the presence of Linux.

    3) If they use Linux, they will probably want to extend some of the kernel, or alter parts of it. But it's GPL!! Now, they can dynamically link to GPLed software and that's okay, but if they want to make any alterations, they hve to distribute them. Now, that might actually make a valid busines plan, but it isn't an option as far as Microsoft is concerned. They don't want anyone seeing any source, if they can help it. The past is evidenc.

    4) This would mean a re-write of either ALL of their software - Office, IE, VisualStudio, BackOffice ... hardly a good idea, giving competitors a few years to catch up in the software stakes. Or they could drastically improve WINE and run their unported Windows software. But what would be the point of moving to Linux and using it to run Windows programs through an emulator? I doubt Microsoft would even consider this option, especially as WINE is GPL, so they'd have to start from scratch.

    Basically, what it boils down to is: compatability with existing and under-development software, and a desire to keep the Windows platform closed to everyone outside of Microsoft.

    Also, MS wants to integrate DRM into the OS. And they definitely don't want anyone getting their hands on the code. So they'd be rather worried about how to distribute the DRM without any legal issues concerning the GPL. They'd have to keep the DRM right away from the core of the OS, which is where they appear to want it to be. (Okay, this is a rather flaky reason, but it may be a small factor).

    --

    This sig intentionally left bla... dammit!
    Who's got the whiteout?
    1. Re:Nice idea, but... by erpbridge · · Score: 3, Informative

      #4... see the OSI chart, Applicaton Layer

      It SHOULDN'T mean a rewrite of all of their software, as the software should just be written to reference to the OS layer below it, not to the Kernel layer below that. The only things that might have problems are things like Visual C++ which, as part of their programming language, has the ability to make direct device calls... which even then should be done via device drivers running in the OS layer.

      Theoretically, the OS should run as an abstraction layer, so that whatever it is running on top of, whether that be a DOS "kernel", NT kernel, Macintosh (before OSX), or Linux or BSD kernel, isn't even something that needs to be addressed by the individual apps.

      Of course, that's in a perfect world, where any windowing system, whether it be MS Windows based, Mac windowing based, or X-Window based, can run on top of any kernel. We don't have a perfect world, and application developers (especially Microsoft ones) are known to code quick and dirty for their specific setup only, not for global compatibility.

      So, yes, for the time being, you are correct.

  15. Cringely a bit confused.. by radon28 · · Score: 3, Insightful

    If you read the article, Cringely seems to have a misconception about how Windows NT works.. he still thinks that Windows is just a binary layer running over a DOS shell, something that hasn't been true since Win9x. The command line in Windows 2K/XP is just an emulation of DOS. Anyway, let's be serious. We all know Microsoft isn't worried about the quality of their products, and certainly wouldn't backpedal the last few years of Unix/Linux bashing (no pun) and do something revolutionary like this.

  16. Utterly ridiculous and wistful by erroneus · · Score: 4, Insightful

    It doesn't save much even when he concludes that it wouldn't likely happen. This is mainly because the idea of Microsoft moving their windowing system over to Linux has been thought of long ago. And If not also by other people, certainly by myself.

    Frankly, I think it would sell all over the place though clearly people would insist on running X with "Microsoft Lindows" anyway... look at people running X with MacOSX.

    It's clear that Linux users need a MUCH better windowing environment, but we've been geared to X for so long that another windowing environment is unimaginable... okay maybe not unimaginable, but so far, not projected to be in wide acceptance.

    I also fear for what would happen if Microsoft got control of the Linux desktop. Instability is a "feature" I firmly believe is part of their marketting strategy. (Provide patches for a while and then stop offering them while pushing the 'next version.') We would always have problems and would never get fixed.

    However, I also see people hackign Windows for Linux by writing compatible libraries and making it free. It is happening with a great deal of stuff in the WINE project... it would just be more complete and more compatible wouldn't it?

    Anyway... it's not going to happen. MS would sooner take FreeBSD and put Windows atop of that.

  17. But then... by Loonacy · · Score: 3, Funny

    MicroSoft could say "Hey, look at how often Linux crashes now!"

  18. Re:OS X by dolson · · Score: 3, Funny

    You mean, like OS X?

    No, he means like Lindows.

  19. Displaying his ignorance by rufusdufus · · Score: 4, Insightful

    Even today, you can still get to a C: prompt under Windows XP, which means a disk operating system is hiding there no matter what Microsoft wants us to believe.

    The command processor has nothing to do with the operating system. This statement displays Mr Cringely's deep ignorance of operating sytems.

    Having worked on development of MSDOS,Window 95 and Windows NT, I can state authoratatively that DOS is not the foundation of windows XP (which is really NT with lipstick). Anybody who knows anything about OS's knows this anyway.

    1. Re:Displaying his ignorance by LostCluster · · Score: 3, Insightful

      It's amazing how many users will think that just because all of the elements visible on the screen are exactly the same, that nothing has changed when they installed a new OS.

      There were worlds of diffence under the hood of Windows ME and Windows 2000... yet they looked almost identical to the common user's eyes.

    2. Re:Displaying his ignorance by Francis+Avila · · Score: 2, Insightful

      Um, lets look at that quote a bit more closely...

      Even today, you can still get to a C: prompt under Windows XP, which means a disk operating system is hiding there no matter what Microsoft wants us to believe.

      He says, somewhere there's a disk operating system, not "DOS". Is this false? Subsitute "disk operating system" for something like "kernel", and I think the jargon will be more clear to you.
      His intention is to counter the MS Market-speak that somehow those 'purty' windows you see is itself the operating system. Which is of course untrue, as you yourself say later...

      The command processor has nothing to do with the operating system.
      Exactly. There's a disk operating system hiding under that command processor, be it a GUI or a command line.

      Also take his statement in the context of the whole article, where it's clear that he understands this distinction. Why would he then act as if he didn't?

      I think you misread "a disk operating system" to == "{MS,DR}DOS"....

  20. They could, but won't (and probably shouldn't) by foonf · · Score: 4, Informative

    Although some of Cringely's comments about the DOS basis of Windows are off-base with regards to modern NT-kernel based versions of windows (the C:\ prompt is there because it has a compatibility layer) the idea that most of what we think of as "Windows" could be ported to a Linux or Unix base is basically correct. Just imagine an officially-sanctioned WINE with its own GUI system and configuration tools...it is not that far from reality.

    But the kernel is neither Windows' biggest problem, nor Linux's greatest asset. By all accounts, the Windows NT kernel is (or at least started out as) a very clean, modular microkernel system. It was built with a POSIX compatibility layer, and actually can host a traditional Unix userspace (and does, if you install the MS "Unix Services" package). On the other hand, Linux is a very straightforward, unexceptional reimplementation of a standard, monolithic Unix kernel, which has become very popular more or less because it works, it is free, and it was there when people needed it. Its novelty is that it allowed for the first complete Free Unix-like system (while *BSD was still in legal limbo). Microsoft could take that kernel, and modify it to run Windows, and neither they, nor we (Linux users), would gain anything...Microsoft would get an operating system more or less like what they have now, except with a pesky kernel under a free-software license, and we would get another version of Windows, which might, with the installation of an X11 server and a raft of libraries, be able to run Linux software, not that anyone would want to.

    If Microsoft tries to "embrace and extend" Unix, they probably won't use Linux, or BSD for that matter. Unlike Apple several years ago, they already have a modern kernel. According to another recent Slashdot story, they are already trying to build a new shell environment based on the existing "Unix services" package, and probably running under the .NET framework. This strategy makes far more sense, both considering the existing strengths of Windows, and Microsoft's emnity toward open-source software.

    --

    "(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
  21. Re:It already is (free) by Znonymous+Coward · · Score: 2, Interesting
    I postied this earlier...

    Even by pirating Windows you are supporting it. Linux can't begin to gain support as a platform until it is widely used. We need to gain market share, please support Linux by throwing away your illegal copy(s) of Windows!

    --

    Karma: The shiznight, mostly because I am the Drizzle.

  22. I like this guy, but... by fireboy1919 · · Score: 4, Funny

    specifically, what a premise.

    Let me start thinking that way.

    You can get to a root prompt in Linux. You can do so in BSD as well. Solaris, also.

    Apparently, these are all actually the same thing - they're all running Linux, underneath it all. And because it's that simple, it's just marketing - since the product is free - Solaris is just hyping it up so that people will use CDE.

    Lets go further. Also, you can find a brain inside every animal. Cats have brains.

    So, deep down, we're all cats, right*?

    *Really old, bad movie quote

    --
    Mod me down and I will become more powerful than you can possibly imagine!
  23. What an idiot by EvilNTUser · · Score: 5, Insightful

    Are we really supposed to take someone who says something like this seriously:

    "Even today, you can still get to a C: prompt under Windows XP, which means a disk operating system is hiding there no matter what Microsoft wants us to believe."

    Clearly the NT kernel is just a big lie, just like NASA never went to the moon. Thank you, Cringely, you have shown me the light!

    And what the hell does he mean by "a disk operating system is hiding there"?? Please, someone, give him a non-disk operating system and see how far he gets after all his drives disappear.

    Besides, it's not the NT kernel that's the problem, it's all the crap MS has put around it.

    --
    My Sig: SEGV
  24. Cringly is poorly informed by ShooterNeo · · Score: 4, Informative

    Cringly is not very well informed in his article. He assumes Windows XP/2k ect are still built on top of DOS. Actually, if he'd read Showstoppers he'd know that the NT kernal was written from scratch, by a group of developers from Digital Equipment Co who set up essentially an independent shop within microsoft to make it. This is why NT is far more stable than earlier versions. The NT kernal is very similar to Unix in how it operates, and essentially is just as good. Also, if he'd read the book he'd know that the DOS command prompt is done via emulation, as well as legacy program support. The core of the system remains NT even when the emulator is running. Anyone who's actually used XP or 2k would find that the vast majority of problems are related to the underlying hardware drivers (this is the ONLY reason why Unix is more stable on some systems, because people building Unix servers use very solid hardware) or to the overlying windowing interface.

    1. Re:Cringly is poorly informed by ShooterNeo · · Score: 2, Informative

      Yes, I forgot that it was VMS the DEC guys were working on. I do know that the client/server architecture it uses (explorer and most NT services are "clients" of an underlying kernal, so if they crash the underlying system keeps running) is similar to Unix. I suspect that the NT kernel might even be better written than Linux (face it, it was written by experienced developers from top schools and there were dozens of em, with clear design goals set by their boss vs. a hacker who just wanted to write his own Unix clone). I don't have access to the code to do a comparion, obviously, but it wouldn't surprise me. From what I read in Showstoppers, 16 bit APP support, while done semi-natively, is done with a translation system that translates the API calls. It is basically emulation, and the developers despaired for a while when it seemed like they were training the OS to run certain progrms (not a general case emulator like they wanted). That is also how XP runs DOS stuff. Believe it or not, Microsoft has known their OSes sucked for a long time, and spent over a hundred million paying NT develepors to correct this (just for the initial development of 1.0. I suspect the tab is over a billion now).

      Their main problem now is that they feel they have to add too many features to keep selling new versions, which greatly increases complexity. This is why their software gets more and more bloated, and why new versions still have many bugs. Their other problem is they basically own their target markets, and to grow any further have to try other sectors, which may not even be profitable ideas. For instance, making web browsers may never be profitable for Microsoft.

      As for using NT in mission critical systems...well, depends on HOW mission critical. While it might be fine for archiving, say, medical data its not good enough to control the electronics of a radiation machine. Nor is it good enough for regulating the cooling system of a nuclear power plant, though it might be fine for running the visitor log at the guard shack. And while it might be fine for the interactive TV system on an airliner, its not for the fly by wire firmware. For this stuff NO OS is acceptable, it has to be written very carefully from scratch, with the software kept as simple as possible. Instead of using multiple threads, the developers will often break the different tasks into different cpus (so that way if one crashes, the other physical chips will keep running). For extreme cases (a rocket?) there will be 3 or more computer systems, each completely independent and running firmware written by completely isolated developers (often in different countries) from a central spec. If one of the computers disagrees, the others will override it.

    2. Re:Cringly is poorly informed by borgboy · · Score: 2, Informative

      The command line to which you refer is the command shell cmd.exe. It has less to do with dos than the Korn shell has to do with bash - at least bash and Korn are 32 bit apps....dos, for all the extenders (such as what came with my old Borland Pascal 7.0 IDE, I think it was PharLap) was never a 32 bit beast. Cmd.exe is a 32-bit NT console-mode shell...that shares much of the old dos syntax. As far as any emulation goes, that's just yet another client subsystem (you do know that NT is a client-server OS, right? Win32 is not the native API on NT, it is just another subsystem, like OS/2 or posix. To run on this parenthetical comment on a bit more, I'll even mention that Win32 is certainly the preferred "language" on NT, though with .Net you can count on that changing. I'll stop Karma whoring now.) called the NT Virtual DOS Machine, or NTVDM. The Windows-On-Windows (WOW) subsystem runs on top of the NTVDM to extend this emulation to 16-bit Windows applications. All 16-bit dos/windows apps run in a single isolated process space by default, unless configured differently.
      In any case, the command shell is no more the OS executive in NT than bash is in GNU/Linux. The kernel houses the executive. And I mean both NT and GNU/Linux here.

      --
      meh.
  25. Re:Are they allowed to? by ender81b · · Score: 2, Informative

    Just the linux source. You can link to GPL'ed software/build stuff on top it/whatever. A number of distro's do this to set themselves apart (like SuSe with YAST).

  26. Now you know why they call him Cringely... by The+Gline · · Score: 3, Funny

    I cringed while reading this.

    --
    Honorary Member of Jackie Chan's Kung Fu Process Servers
  27. No! by ucblockhead · · Score: 2, Insightful

    It's time we stopped trying to shoehorn seventies era multiuser designs (or eighties era single user designs) onto modern PCs. What we really need is an OS redesigned entirely from the ground up for the sort of tasks a modern home or business user needs on the desktop. Linux is no more that then Windows.

    All of the complaints about Linux on the desktop boil down to the fact that it is a clone of an OS designed for minicomputers with multiple users. All of the complains about Windows boild down to the fact that it is an extension of a single-user, single tasking machine.

    In both cases, the OSes have been stretched into something else. In both cases, the stretching has caused problems. Better to start from scratch.

    --
    The cake is a pie
  28. Re:Are they allowed to? by brain159 · · Score: 2, Informative
    that's a common misconception - but if I make some minor tweeks to GNUFoo and sell it as VisualFoo for $75 + tax, I have to sell it under the terms of the GPL, with everything that entails (i.e. every user would then be free to re-modify it and give it away or sell it better and cheaper to compete commercially with me).

    The Free Software Foundation (they who wrote the GNU GPL) have a good FAQ which tells you about as much as you can find out about it without needing a lawyer's advice.

  29. cmd.exe by ucblockhead · · Score: 3, Interesting

    XP actually ships with both cmd.exe and command.com. (command.com works via emulation of the DOS calls, of course, so yes, he's an idiot.)

    --
    The cake is a pie
    1. Re:cmd.exe by cmacb · · Score: 2, Insightful
      "Also, IIRC, Cringely is not one person but a pseudo-name used by a panel of writers. One of them might be a little looney, but the rest might be very well-grounded, and perhaps we are just hearing "Spooky Mulder's" ideas?"

      This article is by one guy, by that name. he used to write for a magazine (PC Week?) under that name and the magazine copyrited the name. That's the panel of writers you are thinking of.

      IMHO, most of the critics here did not read the article, or read it too literally. His general point was that people buy Windows for the user interface, not for its VMS underpinnings or even for DOS.

      PS: I noted the additional reasons they might want to do this in a later post. The suggestion that MS might benefit from a GUI on top of Unix approach is NOT a new prediction, and in fact there are rumors that they are already working on it.

      The reasons they might want to do this go far beyond the technical difficulty issues. They have $40 Billion dollars for petes sake, they could write the whole dang thing from the ground up in Visual Basic if they felt like it!

      (Now just watch someone comment on how ridiculous it would be to re-write Windows in Visual Basic)

    2. Re:cmd.exe by Twirlip+of+the+Mists · · Score: 4, Informative

      Also, IIRC, Cringely is not one person but a pseudo-name used by a panel of writers.

      Not exactly. Robert X. Cringely is kind of like the Dread Pirate Roberts: a serial pseudonym. The name was first used in InfoWorld magazine when Dvorak left-- and started losing his mind, if his last couple years' worth of columns are any evidence-- to replace the famous byline. The Robert X. Cringely we're all most familiar with is really Mark C. Stephens; he's the guy who wrote the books and hosted "Triumph of the Nerds" on PBS and who writes "I, Cringely." He was the third Robert X. Cringely to write for InfoWorld, and he wrote for them for 8 years. Since that Cringely's departure-- okay, firing-- from InfoWorld in '95, many others have written columns under that name for the magazine.

      The real Robert X. Cringely has been retired for 15 years, and living like a king in Patagonia. ;-)

      --

      I write in my journal
  30. platform, application... and service by Anonymous Coward · · Score: 2, Interesting

    MS could only survive in such a mythical model if they concentrated on being a service oriented organization and/or relying on applications such as Office. Why would they want to do this when their business model works perfectly well now? Sure their stuff crashes, is a crackers dream and is always about 5 years behind the *nix world with functionality (but they always have more "features"). However their marketing and legal methods have produced what their lack of engineering and innovation have not, so why change?

  31. Re:sure by MORTAR_COMBAT! · · Score: 3, Insightful

    The world == several billion people.

    95% of the world would be several billion people.

    There are not several billion people running Windows. There are not even a billion people running Windows.

    There are not even a billion people with computers.

    --
    MORTAR COMBAT!
  32. Re:Microsoft could be a lot of things by Squidgee · · Score: 2, Insightful
    >Anything they do, is calculated to turn a profit

    So is anything ANY company does; even your beloved RedHat, or SuSe. The goal of a company is to make a profit. Those cease and desist letters are to protect that; and they have every legal/moral right to protect their own property. What don't the majority of Linux users get about this?

    *Sigh*. Once Linux users see that a business needs to make money, Linux will be viable on the desktop. Until then, none of them will buy Linux often enough to support the business until they gain the desktop. See the Mandrake story currently on the front page for more info on this topic.

  33. Everyone is missing the point. by Jason+Pollock · · Score: 5, Insightful

    Cringley isn't an idiot. You may not agree with what he's saying, you may think that he doesn't understand what an OS is, you may even think that Microsoft would never follow that course, but he isn't an idiot.

    He is talking about Microsoft doing _exactly_ the same thing that Apple has done with OSX (use someone else's OS), except with Linux instead of BSD. Five years ago, would anyone have thought that Apple would use someone else's OS to run their UI? Heresy!

    Is it going to be as easy as simply porting a windowing system? No Way! Does he understand that? Most certainly.

    What he is saying is that Microsoft has demonstrated that it doesn't _need_ to control the underlying OS in order to get everyone to think that they're running the show on the desktop.

    He points out the benefits of moving to Linux or even BSD. Would replacing XP/NT/9X as the OS remove MFC .NET, C#, DirectX or any other API? Nope, it would just use the underlying OS differently. In fact, Wine has done a lot of this already...

    Would Microsoft ever do it? Doubtful, but then I would have sworn that Apple would never use BSD...

    Jason Pollock

    1. Re:Everyone is missing the point. by jpmorgan · · Score: 5, Interesting
      No, Cringley is missing the point, and he's talking about something he doesn't understand: namely the Windows/NT mix.

      In some respects he's right, but accidentally (a stopped clock is right twice a day), in that Windows is built on top of another operating system, in this case, NT. But to transition to another base there are three questions that would have to be answered:

      • Is it possible?
      • Would it be better?
      • Would it be economic?

      Is it possible? Not without a lot of modification to Linux. NT is not UNIX and has a number of fundamentally different idioms; while Win32 abstracts a lot of this, it still pokes through in a few places. Even if Microsoft implemented features in the Linux kernel necessary, they'd still be forced to deprecate half the API and force developers to rewrite their applications to take full advantage of the new architecture. And if they rewrote Linux enough to make this unnecessary, it wouldn't be Linux anymore - it'd be an NT rewrite.

      Would it be better? Cringley simply assumes that Linux is faster, more stable, etc... than NT. Windows is notorious for being unstable, although most of that reputation is due to the Win9x line. Win2K/XP have been known to crash on occasion, but unless you're using some seriously broken hardware, or have fucked its internals up a lot, it doesn't crash that often, and even then the vast majority of crashes are due to the Win32 layer, not NT itself. NT has a stronger security model, is realtime and fully reentrant. In short, the problems with Windows 2000/XP are not the fault of NT, but Win32 itself. Exactly how would porting Win32 to Linux solve these problem?

      Would it be economic? The marginal benefit of porting to Linux would be minimal, and at great expense. I can't see how Microsoft would justify it.

      Cringley suggested something that is fundamentally highly technical without understanding the real issues involved, which was stupid. This is particularly ironic when you consider the section of his site saying that people should listen to him since he knows what he's talking about. Once again this simply proves that he's nothing more than a digital snake-oil salesman - under the guise of holding an expert opinion, he tells people what they want to hear in exchange for ratings.

    2. Re:Everyone is missing the point. by NeuroManson · · Score: 2, Insightful

      The difference between Apple and Microsoft, however, is this:

      Apple: Proprietary hardware and OS, though with a little effort, other operating systems can be installed.

      Microsoft: Proprietary OS, open hardware. Any variety of OS can be installed as an alternative.

      The key word here is proprietary. Apple makes whatever business they have from the proprietary hardware, not the OS. Microsoft makes whatever business they have from the proprietary OS, not the hardware.

      As Microsoft is primarily a software company, they have everything to lose by using an open source kernel which they will have no control over.

      --
      Just because you can mod me down, doesn't mean you're right. Shoes for industry!
    3. Re:Everyone is missing the point. by Sentry21 · · Score: 3, Insightful

      He is talking about Microsoft doing _exactly_ the same thing that Apple has done with OSX (use someone else's OS), except with Linux instead of BSD. Five years ago, would anyone have thought that Apple would use someone else's OS to run their UI? Heresy!

      The difference is that Apple has always been a friendly company - not friendly to everyone, of course, they have to protect their investments, but I look at it this way: Apple may be a 'corporation', which is evil to some, and they may not GPL every line of code ever written, which is evil to others, but they're not anti-competetive (as if they have a chance), and they're not anti-user. MS, on the other hand, is very anti-competetive, and very anti-user. All their software assumes that you're a lying, cheating, thieving bastard, and spies on everything you do. Nice.

      MS makes their money by doing what's best for the company. Apple makes their money by doing what's best for the users. What MS doesn't realize is that in the short term, being a jerk is great, but in the long term, Apple's the one who's going to come out on top.

      The point I'm trying to make, I guess, is that Apple went with BSD because it was the smart thing to do, it was the clever thing to do, and it's paid off big time already. MS will never go with Linux, because then they don't control everything. They can't control Linux kernel development, they can't control apps, they can't control APIs, they can't control hardware, they can't control much of anything, because they'd always have to give the source back. Companies wouldn't want to write Linux drivers, because binary drivers generally suck, and source drivers don't leave a lot of room for trade secrets. MS requires power-control.

      Apple, on the other hand, opened the source, but still keeps a leash on it, in a small sense, and they control the hardware as well, plus the overlying APIs, but Apple's control is quality control, and no one's going to take their quality away from them just by having the source.

      --Dan

    4. Re:Everyone is missing the point. by mangu · · Score: 2, Informative
      I was agreeing with everything you mention, until I got to "...is realtime and fully reentrant."


      The reason I migrated completely from NT to Linux is that a few years ago I was writing a software that did realtime data acquisition from the sound card. It never worked correctly in NT, because, as I found out after much debugging, NT disables interrupts for as long as 100 milliseconds at a time. If you want to do any extensive data processing on an audio stream without gaps in NT, you have three alternatives: (1) write a realtime thread handler that duplicates a lot of the scheduling task, (2) write a new device driver, or (3) do it offline. Strange thing is, Linux is *not* realtime, but my program works fine in it, just goes to show how important a good task scheduler is.

  34. Re:OS X by eggsovereasy · · Score: 3, Insightful

    Did you ever consider that he was makeing an analogy... "MacOS is to Darwin (BSD) as Windows is to Linux" just in case you can't figure it out.

  35. Re:Who? by capnjack41 · · Score: 2, Informative

    I think that Microsoft did develop NT themselves, but with much help from some of the same guy that did VMS (basic googleing turned up this.

  36. The Truth... by Anonvmous+Coward · · Score: 4, Funny

    "Should The Next Windows Be Built On Linux?"

    No because I hate Microsoft and I refuse to see any good that could come from it.

    1. Re:The Truth... by NanoGator · · Score: 2, Funny

      "No because I hate Microsoft and I refuse to see any good that could come from it."

      Heh. If you posted that sooner a bunch of other posts would have been modded as redundant.

      Too bad I don't think anybody'll see the humor in it.

      --
      "Derp de derp."
  37. You're wrong. VMS != UNIX by jpmorgan · · Score: 4, Interesting
    Correct me if I'm wrong, but isn't VMS based off of Unix as well?

    You're wrong. VMS and UNIX appeared at about the same time, but are very different beasts. Arguably, VMS was better than UNIX, but UNIX became dominant as a result of BSD.

    1. Re:You're wrong. VMS != UNIX by John_Sauter · · Score: 3, Informative
      Actually, it was TOPS-10 that appeared at about the same time as UNIX. VMS didn't appear until 1978, but TOPS-10 was one of its ancestors. Descendents of TOPS-10 use the DIR command; descendents of UNIX use the ls command.


      John Sauter (J_Sauter@Empire.Net)

  38. Re:Erm... it isn't already? by jguthrie · · Score: 2, Insightful
    It may come as a shock to you, but I don't particularly give a damn about 'my' market share. I don't need zillions of people choosing what I choose to make it the right choice for me. I use what I like and I will continue use Linux as long as I like it.

    I am fortunate that my employers think Linux is worth using, and it's nice for Linux to have enough popularity that the software tools I need get developed, but they would be there even if the Linux usage had peaked in 1992. Maybe there will be a revolution. Perhaps it's even under way right now. Who knows? I'm not in it for your revolution. It isn't important to me.

  39. MS used to sell UNIX by karlm · · Score: 4, Insightful
    Did they sell exclusive rights to Xenix to SCO, or could they still migrate everything over to the Xenix kernel without having to pay SCO?

    This will NOT happen.

    It's a shame to see MS take things it definately knows about and reinvent them poorly. They knew about UNIX crypt passwords, but went ahead and made the LM hash for passwords but neglected the salt value used in UNIX crypt to prevent parallel cracking of the entire password file. They later saw some of thier problems and came up with the NT hash based on UNIX md5 passwords (but using the md4 hash), again neglecting the UNIX salt. I'm a security systems guy, so maybe it just happens that MS only reinvented poorly the stuff I'm knowledgable about. Using off-the-shelf MIT-liscenced (similar to X11 liscence) Kerberos instead of making up their own networking authentication protocols and having to revise them when they realize they designed them poorly.

    It was a good idea for them to try and make NT a microkernel OS, but it didn't end up working out. It's a shame they didn't reinvent the filesystem as a unified virtual filesystem with C:, D:, etc. being symbolic links for legacy purposes. Oh well.

    --
    Copyright Violation:"theft, piracy"::Anti-Trust Violation:"thermonuclear price terrorism"<-Overly dramatic language.
  40. They could... by dancingmad · · Score: 2, Funny

    MS could just buy Mandrake and not miss a beat...say hello to the new clippy.

    --
    "There is no time, sir, at which ties do not matter," Jeeves, (Jeeves and the Impending Doom)
  41. Maybe this is simplifying it too much but... by techstar25 · · Score: 2, Informative

    Maybe this is simplifying it too much but . . . if Apple put a nice GUI on top of UNIX and called it OS X then why can't Microsoft develop a nice GUI to go on top of Linux and just call it Windows? If the GUI is nice looking enough, most people won't know the difference, so they'd still be able to sell "Windows 2003" for $100 per copy. Now that Apple has done it, MS could probably get away with the same thing.

    1. Re:Maybe this is simplifying it too much but... by evilviper · · Score: 4, Insightful
      why can't Microsoft develop a nice GUI to go on top of Linux and just call it Windows?

      Because Apple was willing to almost completely drop backwards compatibility. Microsoft's entire monopoly is based on backwards compatibility. If they were to say that the next version of Windows wouldn't be able to run most current programs, you would see their share of the desktop market instantly drop like a rock.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  42. It would work by Slime-dogg · · Score: 2, Informative

    The same way that MacOS works. You can distribute the binaries that sit on top of the OS. Just make sure you don't link any of the OS code into your binaries, and you'll be ok.

    --
    You need to restart your computer. Hold down the Power button for several seconds or press the Restart button.
  43. Not aborted! by ucblockhead · · Score: 3, Informative

    That IBM/OS project wasn't aborted! It released OS/2 1.0, which was a fully multitasking OS with no GUI. I believe Microsoft was still involved when OS/2 1.1 was released. This release included Presentation Manager, the first GUI for OS/2.

    Also, your progression for DOS isn't really correct. DOS and Windows were concurrent things for years. All 16-bit versions of Windows required you to actually go out and buy DOS. They weren't just two different things from a technical standpoint. They were two different things from a marketting standpoint. It was really more like:

    DOS 3.0 >> DOS 4.0 >> DOS 5.0 >> DOS 6.0 >> Windows 95
    Windows 1.0 >> Windows 2.0 >> Windows 3.1 >> Windows 95

    --
    The cake is a pie
    1. Re:Not aborted! by quantum+bit · · Score: 2, Funny

      really, I could reboot OS/2 by clicking Ctrl-Alt-Del. Is not it the sign that it is just DOS?

      I can reboot Linux by pressing Ctrl+Alt+Del, that means it must be based on DOS...

  44. Someone is already trying to do this...sorta by angryrobot · · Score: 2, Interesting

    A bunch of folks have already started working on xpde. It aims to be a "transitional" window manager to give people an easier time moving to Linux from from Windows. It's basically a Windows look-alike, but instead of being the end-all like the Microsoft idea, it's meant to give people something that simply looks like windows, so they can get past desktop-shock.

  45. New motto by abe+ferlman · · Score: 2, Funny

    Slashdot
    News for Nerds. Stuff that's never gonna happen.

    --
    microsoftword.mp3 - it doesn't care that they're not words...
  46. Windows Kernels, and Environments by einhverfr · · Score: 5, Informative

    but explorer.exe is not the windowing layer/api, just like Gnome is not X-Window

    Quick and dirty architectural comparisons:

    Linux Kernal -> Windows Kernel
    sh -> cmd.exe
    X server -> GDI.exe
    Window Manager -> Explorer.exe
    CORBA -> (D)COM

    Note these are just quick approximations. My point is that both OS's are reasonably mature and stable (baring spyware, etc.) and there are a lot of areas where both could improve, but porting Windows onto Linux doesn;t make sense for Microsoft today and is a lot more work than Cringly seems to think.

    But then this guy has never seemed to know what he is talking about

    --

    LedgerSMB: Open source Accounting/ERP
    1. Re:Windows Kernels, and Environments by SirSlud · · Score: 4, Funny

      you're bang on, man

      again, we think, who combines the awesomeness of *nix with the gui wikedness of XP? Oh yeah, apple! ;)

      --
      "Old man yells at systemd"
    2. Re:Windows Kernels, and Environments by apweiler · · Score: 3, Informative

      Window Manager -> Explorer.exe

      I disagree here. I don't know much about Windows internals (and I've *never* used WinXP...), but Explorer.exe is probably more equivalent to something like Konqueror (or even KDE as a whole) - integrated Browser/file manager/desktop environment. The window manager would probably be integrated in GDI or something. Hell, I've had (on Win98 though) Explorer.exe crashed and killed, but the system was still sort-of-running, with some windows open (well, the 'end task' box you get when you press Ctrl-alt-del).

  47. Re:Mostly correct. by Anonymous Coward · · Score: 3, Insightful

    but explorer.exe is not the windowing layer/api, just like Gnome is not X-Window

    explorer.exe seems to be what Cringely is talking about when he says "Windows". At least that was my best guess.

    No, I don't think he is smart enough to even know what it is exactly he was referring to... but my guess is more along the lines of the actual Win32 API as embodied in the Csrss.exe subsystem and the core Win32 DLL's (i.e., Kernel32.dll, User32.dll, GDI32.dll, ComDlg32.dll, AdvAPI32.dll, etc.)

    Still, it's hardly even worth speculating since he is such an idiot. Listen, Linux has a lot of strong points and a good future ahead of it, but it is just lunacy to always assume that everything is better with Linux. Banana splits are great. Pepperoni pizza is great. But, that doesn't mean that I want to start putting pepperoni's, cheese, and tomato sauce on my banana splits! Both Windows and Linux will be far better off evolving on their own separate paths, and only a complete layperson would suggest otherwise.


  48. Re:This is just silly by Ziviyr · · Score: 2, Interesting

    Hitting "MS-DOS Prompt" and getting bash would be sweet though. :-)

    --

    Someone set us up the bomb, so shine we are!
  49. But what about the balance?! by Cyb3rt3k · · Score: 2, Interesting

    If for some mysterious, magical reason Windows would be built on Linux, I think it'd be a Bad Thing, not for any technological reason though, but for economical reason.

    A healthy capitalist system requires a diverse eco-system, in this case, various technologies to compete, something like this would just tip the balance too much on one side. The ideal situation is that you have multiple operating systems with roughly equal market share, so they compete against each other to gain more market shares, but ideally, they only temporarily gain a lead.

    I'm pretty certain the open-source movement generally agrees that different approaches to one problem, is a good thing, like KDE, Gnome, Window Maker, BlackBox, etc. No window manager should ever completely dominate the others, because then it stifles improvement.

    *puts on an absestos suit* I wonder how much I'll be flamed this time for posting...

  50. Re:Dumb idea... by evilviper · · Score: 2, Informative

    Linux is a Unix-like system. However, the fact that it is partially based on a 30 year old design does not make it any less advanced.

    Saying: ``The state of the art is way ahead of this" about Linux is like saying the same thing about a recent BMW. Just because it has roughly the same design as something that is very old, does not mean that the modern implimentation is less advanced by any means.

    You could say the state-of-the-art desktop computers of today are obsoltele because they are all based on the Apple II. Sure, technically true, but it's such a gross oversimplification that it doesn't hold up.

    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  51. Separation of operating system and windowing by Animats · · Score: 4, Interesting
    There are arguments for a strong separation between the operating system and the windowing system. NT 3.51 really did have a strong separation between the two. In NT 4/2000/XP, the graphics subsystem moved into the kernel, over the objections of Dave Cutler, the primary architect of NT. This wasn't done to improve performance; it was done so that Windows 95 code could be reused in NT 4, giving NT and Win95 closer graphics semantics.

    More and more junk has been going into the kernel ever since. The multimedia codecs have moved into the Win2000/XP kernel, for example. Start coding your viruses now.

  52. When non-techies try to fake it... by Eric+Damron · · Score: 2, Insightful

    "Even today, you can still get to a C: prompt under Windows XP, which means a disk operating system is hiding there no matter what Microsoft wants us to believe."

    This is pretty much total crap. Yes, you can bring up a C prompt. Does that mean that XP sits on top of DOS? No. What you are doing is running a type of "DOS emulator." It's not really DOS at all.

    "Windows XP is not an operating system. It is a windowing system that sits atop an operating system much as KDE or Gnome sit atop Linux."

    Nope... Total crap here.

    Windows, Windows 95, 98 and I believe ME are one branch. Windows NT is a completely different code base. NT, 2000 and I believe XP are all from the same code base.

    --
    The race isn't always to the swift... but that's the way to bet!
  53. There may be some truth to this already... by neoevans · · Score: 2, Interesting

    I always had a suspision that underneath it all, Windows (NT especially) was running atop of some bastardized form of Unix. Think about it.
    What was there 30+ years ago but Unix? Isn't it the grandfather of all anyways? Try this:

    -Open the management console in Windows 2000 (the one called "Manage" when you right-click My Computer).
    -Select "System Information", expand the "Software Environment" folder and select "Loaded Modules".

    In pre-SP1 builds of Win2K the dates on some of the DLLs in this folder were in the 1970's. How can that be? Windows wasn't even around in the 70's! Isn't it possible the kernel is already based on Unix and 'Windows' is just another abstraction layer? It sure would account for the mediocre performance (added overhead).
    And some of the hardware names in the registry are Unix-like. Check:

    \HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\H ivelist
    You can see the OS locates volumes the same way Unix does. For example, the location of Registry file \REGISTRY\MACHINE\SAM is:

    \Device\HarddiskVolume1\WINNT\System32\Config\SA M

    So what if the '/' is a '\'? It's the same thing right?
    After all...

    "...The greatest trick the devil ever made was convincing the world he didn't exist..."

    I know, corny one...;)

    --
    "You are not a beautiful and unique snowflake."...Tyler Durden
  54. Re:OS X by Twirlip+of+the+Mists · · Score: 2, Informative

    It's built with Apple's proprietary Mach kernel

    How do you define "proprietary?" Mach started at CMU as a totally open-source project; NeXT used CMU's Mach kernel as the basis for NeXTstep, which evolved into OS X. Apple's fork of Mach (which really isn't Mach any more, in some important ways) is still open-source.

    All too often, "proprietary" is a dirty word that's thrown around Slashdot to mean "not what I'm using."

    I can download some GNU utilities and copy them to C:\WINNT, now is my OS based on GNU?

    Well, considering that GNU is neither a kernel nor an operating system, but rather just a loosely associated collection of utilities, I'd say that no operating system is "based on" GNU.

    --

    I write in my journal
  55. Wanted to? by Ancil · · Score: 2, Insightful

    Microsoft has $40 billion dollars in cash tucked away.

    If they wanted to, the could be the world's biggest just-about-anything.

  56. Perhaps we should let windows be windows geez! by The+B · · Score: 2, Interesting

    This is ridiculous. MS persists to achieve its goals, achieve them amidst years of laughter and jokes from Mr Big Iron. Its a bit late Linux. I'm sure you'll mature, but you need the apps. Then again perhaps this article just proves what I've said before. Linux just turns more into windows with every so called improvement. Why build what already exists.

  57. why?? by smash · · Score: 2, Interesting
    Why would they use Linux, when FreeBSD is available under a less restrictive license.

    Now before the Linux purists get started up and start modding me as flamebait - I use both Linux and FreeBSD (Linux since 96, BSD since 2000) and although I'm partial to FreeBSD myself, I have nothing serious against either one...

    Parts of Windows have used BSD derived code in the past, such as the TCP/IP stack (which may have since been rewritten), and MS is a lot friendlier to FreeBSD than linux (C# anyone?).

    Barring legalities, the whole FreeBSD vs Linux argument is a matter of personal preference at the moment for most people. So Linux does better SMP at the moment? How many desktop users have SMP desktop machines out there? Amongst the *geeks* maybe 10%. I've run both extensively and as far as performance goes, there's not enough in it to bicker about.

    Again, the BSD license is a lot more compatible with MS - they can base Windows 2008 on xBSD and not have to open the source up at all if they like!

    smash.

    --
    I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  58. Re:Who? by rusty+spoon · · Score: 2

    You mean "They hired smart people"?

  59. XP better than Linux (flamebait?) by forged · · Score: 2, Insightful

    From the article:

    • Linux is better, faster, stronger than whatever is living underneath XP now, right? Performance would improve.

    I actually have a positive experience after having -finally- moved from 98SE and ME to XP, and despite my very low expectations about XP, I have to admit that it's not working too badly after all, to say the least.

    Don't get me wrong, I'm also a happy Linux user since 1994. But with XP I can actually see Microsoft catching up with Linux regarding stability, performance and features....

  60. No basis by ajole · · Score: 2, Interesting

    This article has almost no validity. When you use windows, you get a feeling of reliability and an *speed*. I'm writing an audio application that has very tight time-performance constraints, and I'm finding MFC's threads and gui widgets to be by far the quickest over qt. Why? its native. Don't flame me about qt not being linux. if you do you've missed the point.
    The point IS that MFC is native. N-A-T-I-V-E. In the windows sense that means its going to deal with the K-E-R-N-E-L better, and anything else that has to do with the windows platform.
    Windows XP is not just a windowing system. It is more complete than linux. I don't like XP for various reasons, but that doesn't change how a business makes decisions. point is, if this all this was true windows WOULD be, how was that? "kissing the ring of linux?"

    --
    -P ...and the boy pulled open his bleary eyes an discovered the python he always knew he was.
  61. What REALLY Lies Beneath: by jsherring · · Score: 2, Funny

    What Lies Beneath: Why Cringley Should Write His Next Article on Toilet Paper

    I was discussing this article with a friend, and he suggested that Cringley should write his next article on toilet paper. And you know, it actually makes some sense!

  62. Article makes me cringe by thasmudyan · · Score: 4, Informative

    It's been a long time that I read such completely bogus. I don't want to flame but I have to. Here it goes:

    Even today, you can still get to a C: prompt under Windows XP, which means a disk operating system is hiding there no matter what Microsoft wants us to believe.

    What a bunch of crap! So there is still a "disk operating system" under Linux because I can open a shell window, too? Man, what are you talking about?

    DOS 7.1 brought the FAT32 file system to Win95, not the other way around

    So what, FAT32 is a file system, and now - ? What does that say about the operating system? Nothing? Right.

    Windows XP is not an operating system. It is a windowing system that sits atop an operating system much as KDE or Gnome sit atop Linux.

    What's this guy's definition of an operating system? First, Windows has its OWN KERNEL (microkernel, btw). Second, it has its OWN DEVICE DRIVER and SOFTWARE ARCHITECTURE. While I can agree that KDE/Gnome do a fairly large and important part of the work that non-Linux OSes provide as a whole package, Windows is doing ALL THE STUFF an OS does with *no* underlying foreign kernel or architecture.

    The history of DR-DOS is especially interesting because it went through so many hands. [....]

    Blah, blah, blah... where's all that DOS talk supposed to get us? Does it really make sense to talk about legacy crap like that? And if so, should we really begin to talk about text-mode-only Linux, from back in the days, also? What about legacy mainframe interfaces? Why? To prove the point that DOS is underlying of Windows just as Linux is the underlying architecture to KDE? WTF???

    Now back to Microsoft putting Windows on top of Linux. Linux is better, faster, stronger than whatever is living underneath XP now, right? Performance would improve.

    Give me a break here! Driver support for Windows often leads to much better performance (because PC manufacturers really cater to the Windows monopoly).

    Apple has made a virtue of doing exactly this with MacOS-X, heralding its Mach kernel and BSD roots. Couldn't Microsoft do the same?

    MacOS-X is a completely new system, it has a legacy-app compatibility layer (like Wine is for Linux) but otherwise it's a complete new system. And, they HAD to do it, because OS 9 and below where such utter crap (from a purely technical point of view, mind you). If MS where to switch (for whatever stupid reasons) to a *nix kernel like BSD or Linux they would have to provide a complete legacy Windows version inside the new system just to provide backwards-compatibility. And boy would *that* be slow! And, again, why??? It would mean to develop *LOADS* of new device drivers and APIs - for what?

    I could go on like this forever. Articles like that make me want to puke. It would be suicide for MS if they did something like that, especially now, the first time they have a workable OS with Win2000/XP. Why oh why?

    OK, I asked for it. Bomb me, I don't really care. Cringely articles I actually liked them in the past, but what the fuck is this load of crap supposed to be?

  63. In the Real World by tarawa · · Score: 2, Insightful

    First, the idea of porting the Windows into Linux has been around for a long long long long time. It's always had it's supporters and dissenters, so far nothing in this string of posts have contributed anything new to the argument.

    It comes down to getting decent apps on the Linux platform, and I know I'm probably gonna get flamed for this, but 95% of the software honestly sucks. At least Windows apps generally conform to a standard and typically very polished. Yes, I know that Linux apps are getting better, but they aren't there yet and why we all argue about every little thing, Microsoft moves on to the their next version, happy to throw something at the Linux community to get it all rialled up.

    So far, the only version of Linux that I see as promising is Xandros and that's because they are in control rather than 5 million whiney geeks, hackers, cracker, dweebs, or whatever we call ourselves today.

    Second, every OS out there sucks. They all do. Windows X.X, MacOS X.X, Linux and every other OS that is out there sucks.

    I would love nothing better than to see a free, open source OS dominate the market because it is fast, stable, and actually easy to use. Linux is 2 out of 3. Windows XP is generally fast, stable, and a lot easier to use than Linux. MacOS X is fast, stable, and easy to use to a certain group of people while the rest think it is either moronic or insulting to use. In my book that puts Linux at 2 out of 3 while XP and MacOS are at 2.5. Perhaps Linux, in it current form, isn't the answer for the desktop. Maybe the GNU community needs to develope an OS from the ground up that is geared towards the Desktop, and let Linux handle the server and workstation market (where it is competeing extremely well). That way we aren't wasting are time trying to make the Swiss Army Knife of the OS world.

    Oh, BTW, DOS under NT, 2000, and XP is an emulator, just like DOSEMU in Linux. It provides enough of DOS so that many, but not all, old DOS programs will run. The great part is that since those DOS apps run inside a Windows app, if the DOS program pukes, it doesn't take the OS with it like what used to happen under Win 3.x and Win 9.x.

    Finally, here is a link to a funny song that helps make my point on OSes sucking. :) It should make at least some of giggle. :)

    Cya L8r
    Lee

  64. Instead of building it on Linux by sielwolf · · Score: 2, Interesting

    How about on the GNU/Hurd? They could make some Win32, OS/2 modules and work it in over an architecture that's going to try and be compatible with a horde of *nixes.

    But then the question is: if a company makes a proprietary component on the Hurd, would they have to release the source as per the GPL?

    --
    What is music when you despise all sound?
  65. No by Hard_Code · · Score: 2, Insightful

    "Even today, you can still get to a C: prompt under Windows XP, which means a disk operating system is hiding there no matter what Microsoft wants us to believe."

    WRONG. From NT onward, Windows has been an entirely new OS, not a windowing system "running on" DOS. Yes, NT/2000/XP etc have a command processor that LOOKS like DOS, and in fact they have DOS emulation SUPPORT (including the familiar "command.com" binary), but that does not mean they run on it, any more than it means Lindows runs on DOS because of Wine, or that any machine is running on Amiga just because it has an Amiga emulator.

    _Showstopper_ is a good read.

    --

    It's 10 PM. Do you know if you're un-American?
  66. Why? by NineNine · · Score: 2

    What's the point, exactly? Why would MS bother? The NT kernel is stable, fast, and secure if you want it secure. Why would the re-invent the wheel? They've *finally* come out with a good product for the consumers (businesses have been using NT for a long time). After all of these years, and all of this work, why in the *hell* would they suddenly decide to start back at the drawing board again? That was one of the stupidest, for lack of a better word, article that I've read in a *long* time.

  67. Gee I wonder why Microsoft hasn't jumped at this? by thehunger · · Score: 2, Funny

    > If Microsoft wanted to, they could be the world's largest vendor of Free software .. couldn't they?

    Gee what where they THINKING?!

    "Wow! We could become the world's largest vendor of Free software!"
    -Or-
    "we continue to be the world's largest vendor of software that people PAY for.."

    Is it still mindboggling? Why is this even a thread?

  68. for D in seq 0 1000000; do echo "c: != DOS" done by MadFarmAnimalz · · Score: 3, Interesting

    WTF? Slashdot was never this lame... I've been forced to browse at +5 and I've seen a bazillion posts explaining how smart the poster is that he knows that cmd.exe is not DOS, and how Cringely is by comparison.

    If an explanation of why cmd.exe is not DOS +5 interesting gets modded +5, then there's too many mod points floating around. That's what you get when you mod karma whores +5.

    This is NOT meant to be a troll. Slashdot used to be better than this.

    --
    Blearf. Blearf, I say.
  69. Linux? Give me a break! by incripshin · · Score: 2, Insightful
    First off, Microsoft despises Linux. If they were to turn around and give the penguin a big ol' hug, they'd look like hypocrites. Nobody likes being thought of as a hypocrite.

    But that doesn't mean M$ would give up on basing their OS on other existing OSes. There's always BSD. If you had any memory at all, you'd remember the /. story Why Unix is better than Windows... By Microsoft. M$ goes on and on about all the things BSD does better than Windows. And who could forget that Hotmail used to be run on BSD.

    Don't expect Windows 2004 to be based on Linux. It'd be BSD if anything (and if they give a rat's behind about security, they should go with OpenBSD ... but that's just me).

    And you KNOW this.

  70. Mascot? by NeuroMorphus · · Score: 2, Funny

    I wonder which mascot they will use...Personally, I'd prefer tux rather than some dancing orangutang. ;)

    --

    python >>>
    reduce(lambda x,y:x+y,map(lambda x:chr(ord(x)^42),tuple('zS^BED\nX_FOY\x0b')))