Slashdot Mirror


Vista vs. Cairo - A Microsoft History Lesson

avocade writes "Here is a nice history lesson by (the unfortunately infamous) Daniel Eran, arguing why the Longhorn/Vista road is very similar to the NT/Cairo road that Microsoft took in the 90's, effectively trying their best to discourage competition in the marketplace."

194 comments

  1. Not a great comparison... by bigtomrodney · · Score: 0

    Wouldn't it be more accurate to compare NT/Cairo with Vista/Singularity?

    --
    I never get used to these constant resurrections
    1. Re:Not a great comparison... by mrlpz · · Score: 1

      I don't think so, because Singularity is meant to be a OB managed OS ( going from every eventuality the MS Res folks have spoken about publicly ...look at the video for Singularity IV: The return of the UI ), where Cairo was meant as simply an OB OS ( object based OS ) where at the user level their interaction was purely on "tangible" objects ( pictures, videos, documents, etc. ).

      I think where Singularity is headed as towards being the basis of a virtualized OS hosted by a "singularity" kernel that hosts all singularity client OS's. This concept is a grander extension of what Mach was in the late 80's-early 90's, and frankly, if anyone ever remembers something called "Workplace OS" from IBM, they'll say "Aha!" to themselves, and realize this is similar to where MS Res is headed towards. Nevermind that "Workplace OS" was aimed at more "concrete" OS clients ( those who were there will remember them referred to as "Personalities" ).

      Ahh the great days of operating system development. What I wouldn't give to be back in the thick of that once more.

  2. Cairo vs NT/Cairo by DreadSpoon · · Score: 4, Informative

    This article has a confusing title, given that dominance of the Cairo graphics library these days.

    1. Re:Cairo vs NT/Cairo by 6Yankee · · Score: 5, Funny

      Even more confusing when you read it as "Vista vs. Casio", and look forward to a story about a digital watch being forced to run Vista and bursting into flames :(

    2. Re:Cairo vs NT/Cairo by julesh · · Score: 1

      This article has a confusing title, given that dominance of the Cairo graphics library these days.

      Some of us get confused and think articles are talking about NT4 when they mention the graphics library. I guess it's a young v. middle-aged thing.

    3. Re:Cairo vs NT/Cairo by Anonymous Coward · · Score: 0

      Windows "Cairo" led to Windows XP. Yes, there is a weird development history where project cairo was diverted in various ways, but the Greek Letters XP are "Chi-Rho", pronounced "K-eye row". It's interesting that it's often an abbreviation for Christ for those christians out there. Often depicted as a P with an x through the leg of the P. Microsoft has prophecies regarding Cairo as the Second Coming, signalling the End of Days.... it.... uh.... it was foretold.

    4. Re:Cairo vs NT/Cairo by Anonymous Coward · · Score: 0

      Rho gets transliterated into R, not P. Pi gets transliterated into P. Not claiming you're wrong -- MS might have made the same mistake.

    5. Re:Cairo vs NT/Cairo by hackwrench · · Score: 1

      I'm 30 and think the Microsoft code name, though I don't bind it so tightly to NT partially on account of the interface shipping with 95, and the object filesystem a no go.
      http://en.wikipedia.org/wiki/Cairo_(operating_syst em)

  3. Infamous indeed - spammer by mccalli · · Score: 5, Informative

    Daniel Eran has been spamming uk.comp.sys.mac for weeks now, ignoring every polite request for him to stop. He shows no sign of engaging with the group (beyond calling us "a hateful bunch of queens"), just spams links to his blog against charter and then swans off again.

    Daniel Eran. Just Say No.

    Cheers,
    Ian

    1. Re:Infamous indeed - spammer by cloricus · · Score: 4, Funny

      We don't have to; His server is already slashdotted!
       
      Maybe he is still running an early 90s NT server?

      --
      I ate your fish.
    2. Re:Infamous indeed - spammer by cpct0 · · Score: 2, Insightful

      Hmm, I don't want to sound any less stupid than I really am, but other than people using some signature on their Usenet mails, anyone can really make themselves appear to be anyone else on Usenet don't they? I've known these kinds in *cough* less respectable places, where they would get annoyed by the group, then suddenly prove they got no life and spam the heck out of the place with semi-plausible stuff, named against the member that pissed them off or simply ripping out the place.

      Not making an apology, just saying it's a possibility. Then I haven't followed the drama there, so can't tell. I find his articles well written, with an obvious agenda, and repeatingly hitting the nail until we're tired of hearing about that point of view in long rants on nearly the same topic. Interesting point of view. I just wonder what that guy does because he surely got a lot of spare time since ... well ... forever ;)

    3. Re:Infamous indeed - spammer by Anonymous Coward · · Score: 1, Informative

      That is because he has been banned from spamming on digg and has instead been spamming Slashdot [and apparently USENET] recently. Whatever his real motivations may be, the incentive of those advertising clicks must be really something for him.

    4. Re:Infamous indeed - spammer by davecarlotub · · Score: 2, Interesting

      There are 15 messages from DanielEran in uk.comp.sys.mac since November 12th. They are indeed blog link posts, but hardly a FLOOD.

    5. Re:Infamous indeed - spammer by Anonymous Coward · · Score: 1, Insightful

      Calling RoughlyDrafted a spammer is ridiculous.

      The dude writes a blog and submits articles to Digg and other sites, and plenty of other people submit his articles because he's a great writer, even if you can't agree with every idea he has. He writes about topics other news sites skirt and avoid. He also presents an interesting historical viewpoint based on working in tech for a long time.

      Read comments on his site, and its the ignorant 15 year old Xbox fanboys who attack him, while the aged veterans of the tech say he gets everything right. Lots of sources, refers to other writers, and is sometimes very funny. Sometimes over the top, but he is worthy to read.

      As a webhost, I know he's not making anything significant with a few iTunes ads and some Amazon links on the side. Every website from CNET to Digg has far more ads all over, let along the Mac related news/trivia/rumors websites.

      It says something that you bring out the big guns of "spammer conspiracy" ... did he write an unflattering article about you or your pet company at some point?

    6. Re:Infamous indeed - spammer by triso · · Score: 1

      Daniel Eran has been spamming uk.comp.sys.mac for weeks now, ignoring every polite request for him to stop. How do you know it is Mr. Eran posting those messages?

    7. Re:Infamous indeed - spammer by mccalli · · Score: 2, Informative

      How do you know it is Mr. Eran posting those messages?

      Because he states he is, has stated he is in replies and has taken part in email conversations with members of the group - see this thread for more details.

      Cheers,
      Ian

  4. Perfect Timing by Joebert · · Score: 2, Funny

    I shit you not, I was listening to the Wizard Of Oz on TV in the background when I opened this story.
    Coincidence ?
    I think not.


    On a serious note, if it worked before, why do anything different ?
    Are you trying to tell me that Microsoft doesn't have all the money ?

    --
    Wanna fight ? Bend over, stick your head up your ass, and fight for air.
    1. Re:Perfect Timing by FrankNFurter · · Score: 1

      Offtopic: The Wizard of Oz was on TV here as well earlier today.

      Ontopic: Am I the only one who thinks the author of TFA is a NeXT nostalgic? Most of the article (as well as other articles on the site, like the one about Taligent/Pink) were mostly about how NeXT had all the technology long before the competition - which is true - and how NeXT was hurt by the evil empire's vapourware announcement about NT/Cairo.

      --
      "Slashdot - the one place on the internet where guys brag about how small it is." - that IT girl
    2. Re:Perfect Timing by Joebert · · Score: 1

      Right about now, two people are thinking

      Who's NeXT ?

      However, they are not thinking in the same context.

      I'm the one that doesn't know who this "NeXT" entity is.

      --
      Wanna fight ? Bend over, stick your head up your ass, and fight for air.
    3. Re:Perfect Timing by FrankNFurter · · Score: 1

      They were NeXT.

      --
      "Slashdot - the one place on the internet where guys brag about how small it is." - that IT girl
    4. Re:Perfect Timing by FrankNFurter · · Score: 2, Informative

      Damn, I need to preview my posts.

      They were NeXT.

      --
      "Slashdot - the one place on the internet where guys brag about how small it is." - that IT girl
    5. Re:Perfect Timing by Joebert · · Score: 1
      NeXTSTEP 3.x was later ported to PA-RISC and SPARC based platforms, for a total of four versions including NeXTSTEP/NeXT (for NeXT's 68k "black boxes"), NeXTSTEP/Intel, NeXTSTEP/PA-RISC and NeXTSTEP/SPARC. Although these ports were not widely used, NeXTSTEP gained popularity at institutions such as the National Reconnaissance Office, Central Intelligence Agency, First Chicago NBD, Swiss Bank Corporation, and other organizations due to its programming model.

      Looks like NeXT was just destined to remain in the shade.
      --
      Wanna fight ? Bend over, stick your head up your ass, and fight for air.
    6. Re:Perfect Timing by MicrosoftRepresentit · · Score: 0, Offtopic

      Of course the Wizard of Oz was on, its fucking christmas. If theres anything thats guarunteed to happen at Christmas, its that that fucking girl and strawman sex pest is going to be on the tv.

    7. Re:Perfect Timing by TheRaven64 · · Score: 3, Informative
      NeXT was the company Steve Jobs founded after he left Apple. Their aim was to build the perfect computer, and many people believe they succeeded. Most who don't will concede that they came as close as was possible with the hardware of the time.

      Some of their achievements include:

      • An OS with a driver framework written in a dynamic, object-oriented language (Objective-C), making it very easy to write drivers for.
      • The first Rapid Application Development system.
      • The first web browser was written on one of their systems.
      • A very powerful and flexible web development environment.
      • EOF, a transparent object-relational mapping a decade or so before Ruby-on-Rails made the idea popular.
      And lots of others. In the early '90s, they worked with Sun to create a standard to sit on top of POSIX and provide a portable way of writing GUI programs. Sun eventually dropped it, but the GNU project has an implementation, and it's the standard way of developing software on OS X (the latest version of the NeXT operating system, renamed after Apple bought NeXT).
      --
      I am TheRaven on Soylent News
    8. Re:Perfect Timing by DECS · · Score: 2, Interesting

      NeXT offered the world an open standard for a graphical Unix powered by object oriented frameworks called OpenStep.

      Sun and HP signed up to deliver OpenStep compliant, interoperable implementations for their operating sytems (Solaris and HP/UX) and GNU started work on GNUStep.

      The competition was Cairo (Microsoft's vaporware that never materialized) and Taligent (IBM & Apple's vaporware that never materialized).

      Despite being futuristic technology, open, and free, it was dumped upon by its own backers. Sun dumped NeXT for Java hype, and HP joined Taligent just prior to its failing, leaving a void that Microsoft could fill with nothing special.

      Apple bought NeXT and repurposed its technology to build Mac OS X. Nobody says much about Taligent or JavaStations anymore, and Vista is struggling to look like Mac OS X. I guess you could say the whole desktop world fumbled the ball, and Apple happened to be in the right place at the right time to grab the ball and run with it.

      The Secrets of Pink, Taligent, Copland (and OpenStep)

    9. Re:Perfect Timing by StikyPad · · Score: 1

      Yeah, I love that part when "Money" starts playing and the movie goes color. So appropriate.

  5. Win95 just a "polish" of Win 3.0 by ksalter · · Score: 1

    I guess I was under the mistaken impression that Windows 95 was just more than just a "polished" version of Windows 3.0. That's what happens when you look at something objectively. I need to reevaulate my view of Windows 95 and Microsoft and add a lot more irrational hatred. :end of sarcasm

  6. I discourage competition all the time... by dada21 · · Score: 2, Insightful

    That's part of competing -- to give your customers EVERY reason to pick you over someone else. Any good business does it by:

    1. Providing a product that meets the current needs of their customers.
    2. Providing a path to new features/efficiencies for their customers' futures.
    3. Working with third parties to offer incentives to provide your product solely.
    4. Providing a proven ROI for a short-term and long-term focus.

    Microsoft, to me, is not a monopoly -- except when the State is involved (providing patents and copyrights and trademarks). I'm against those monopoly provisions, but those are "legal" ones. Without them, Microsoft's power over competitors would be equalized. You can't blame Microsoft for taking advantage of what you, the voters, allowed them to utilize. The judgements against them calling them a monopoly are only there because you, the voters, let those policies become standard based on Microsoft's given legal priviledge over competition. Nothing prevents competition from doing what Microsoft does -- except than the competition would rather use THEIR monkeys in government to try to stem Microsoft's growth.

    As we see in the relatively free and unencumbered market of the web, Microsoft doesn't have any sort of monopoly -- people are free to choose what they want, and they do. In fact, the long tail effect shows that many products openly compete with Microsoft -- both legally obtained products and illegally obtained ones.

    The whole Vista issue is a non-issue. Everyone who cries foul against Microsoft refuses to see that the products they prefer just don't meet the top 4 items I listed -- in fact, some of them fail most or all of them. No one will invest in a product, even a free one, if it doesn't offer those items. Many Microsoft products do -- but not all of them. Vista will succeed only because consultants will like its standardization, manufacturers will like knowing there is a standard interface for their hardware/software to run on, and resellers will like it because it has always worked well enough for both the casual and the power user.

    Who cares about it looking like past products? If it worked for Microsoft in the past, why wouldn't they follow through with similar performances -- and making new ones to try to produce a better selling product?

  7. WTF by Timesprout · · Score: 3, Informative

    Article rambles all over the place, seems more to be pleading for reader to look at previous articles by author rather than make its higly convoluted point. Reads like a lot of sour grapes about historical irrelevance so I assume the author is just looking for hits by trying to be inflamatory.

    --
    Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
    What truth?
    There is no dupe
    1. Re:WTF by ticklish2day · · Score: 1

      So much FUD. He's got a pretty looking site though -- with all those links to Apple properties.

    2. Re:WTF by DECS · · Score: 1

      The point is pretty clear: Microsoft gamed the world through the 90's by promising to outdo the competition, but ended up not even matching it ten years later.

      Rinse, repeat. The same thing happened in the 80s and again in our decade. You chose to ignore all this, but it doesn't make the facts go away. Everyone hails Microsoft as an innovator and highly successful, but ignores the fact that it has trampled up on real innovation, and outside its monopolies, has been a huge failure.

      Calling the truth "inflammatory" just means you prefer your face buried in the cool sand.

      The Secret Failures of Microsoft
      The Two Faced Monster Inside Zune

  8. How else do you get a message out? by msobkow · · Score: 0, Troll

    If an individual has a message they feel is important that they want to get out, I don't see an issue with posting a reference or two. Flooding a board is another story.

    Besides, using the term "SPAM" is inaccurate: what is the commercial benefit of his links?

    Or are you trying to use distactics to distract people from his core argument, building up hatred by labelling him a spammer?

    --
    I do not fail; I succeed at finding out what does not work.
    1. Re:How else do you get a message out? by mccalli · · Score: 4, Interesting

      If an individual has a message they feel is important that they want to get out, I don't see an issue with posting a reference or two. Flooding a board is another story.

      ...and flooding is what's taking place. Yes, a post such as "here's a new and interesting Apple-related blog, please come and have a look" would have gone down fine. Instead we get every single article he writes for this blog being dumped as a rhetorical question into a group which specifically forbids advertising, and then he never engages in any discussion regarding it. The regulars of the group have all asked him to stop. He just totally disregards us.

      Besides, using the term "SPAM" is inaccurate: what is the commercial benefit of his links?

      Advertising revenue. He's abusing a community discussion group to take every opportunity to dump links to his advert revenue-driven blog. The group does not exist for his enrichment, as we say on there: uk.comp.sys.mac.adverts is thataway -->.

      Cheers,
      Ian

    2. Re:How else do you get a message out? by johnw · · Score: 2, Informative

      Besides, using the term "SPAM" is inaccurate: what is the commercial benefit of his links? Nothing in the definition of Spam requires it to be commercial in nature. The term originated on Usenet and referred to the constant repetition of a message - as in the Monty Python Spam sketch. For a long time a distinction was made between Spam (repeated messages) and UCE (Unsolicited Commercial E-mail). Alas, such a distinction is too subtle for your average journalist to comprehend so now the one term is used for both.
    3. Re:How else do you get a message out? by Jah-Wren+Ryel · · Score: 3, Informative

      Besides, using the term "SPAM" is inaccurate: what is the commercial benefit of his links?

      Why do you think SPAM implies commercial benefit? One of the earliest spammers was an 'evanglist' - sending out generic jesus-freak messages.

      --
      When information is power, privacy is freedom.
    4. Re:How else do you get a message out? by Anonymous Coward · · Score: 0

      Actually, if you actually go to uk.comp.sys.mac you see a nonstop cascade of vitreol laced with homosexual innuendo about nearly everything.

      The response to DE posting a Mac related article (to a Mac newsgroup!) was comments about him being a sexual predator, various gay comments, and a campaign among 3-4 people to sign him up for spam and attack his website.

      Sounds like typical Usenet bullshit, although Ian is posting his hateful screed anywhere he can manage.

      In fact, some of the most vitreolic bitchiness comes from people who had earlier posted articles from RDM to the newsgroup, but were offended when DE/the author did. WTF?

    5. Re:How else do you get a message out? by blincoln · · Score: 1

      For a long time a distinction was made between Spam (repeated messages) and UCE (Unsolicited Commercial E-mail).

      That must have been before my time, and I was reading USENET in 1991.

      I always took "spam" to be related to the mass-crossposting of off-topic messages, e.g. "Make money fast!" Crossposting, USENET-style, isn't something that really applies anywhere else (except some of the old BBS software that was networked in batch mode), and it makes replies to mass-crossposted off-topic messages particularly annoying.

      --
      "...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
    6. Re:How else do you get a message out? by Anonymous Coward · · Score: 0
      Why do you think SPAM implies commercial benefit? One of the earliest spammers was an 'evanglist' - sending out generic jesus-freak messages.

      Similarly, why do you think religions are not commercial enterprises? Scientology only exists because L. Ron Hubbard realized the tax implications of running particular types of businesses.

      A meta-thought: all communication is done to control.

  9. Microsoft lost the war long ago by locksmith101 · · Score: 1

    I don't really get all that vista hype...I really don't. If you ask me, Microsoft lost this battle over the market, once Google stepped up and became what it is today. Google changed all the rules - and the battle now is not about advanced graphical layout and trifles of sorts, but about offering real and valuable services to the users. Microsoft is like the last mammoth - it's huge and strong, but alas, belongs to a dying breed.

    1. Re:Microsoft lost the war long ago by Anonymous Coward · · Score: 2, Funny

      Ya, A high traffic web site vs. the company that runs 90% of personal computers.. They are done for. In other news, the Java platform is posed to take over as the predominant OS.

    2. Re:Microsoft lost the war long ago by canuck57 · · Score: 1

      I don't really get all that vista hype...I really don't. If you ask me, Microsoft lost this battle over the market, once Google stepped up and became what it is today. Google changed all the rules - ...

      Would it not be so kewl if Google came out software and games support, perhaps their own destop/Linux?

      Google certainly is in a position to take on M$ for anything it wants, including OS.

    3. Re:Microsoft lost the war long ago by sbben · · Score: 1

      I see your point, and its valid. As of now Google offers nothing unless you can get to the site. Most people will be doing so with IE on a windows box.

      But! Google is changing the way many people look at these giant corporations. No, I am not a GoogleOS conspiracy theorist but I do think people will come to expect more from a company like Microsoft after seeing what Google has done (with little to no backstabbing and expression of malice towards its users like Microsoft has done with things such as WGA and activation).

    4. Re:Microsoft lost the war long ago by SEMW · · Score: 1

      I can't find the quote, but I'm pretty certain the Google have categorically denied that they are making their own OS or planning to do so. That given, "this battle over the market" doesn't actually seem to exist, let alone be something that Microsoft has "lost".

      --
      What's purple and commutes? An Abelian grape.
    5. Re:Microsoft lost the war long ago by Anonymous Coward · · Score: 0

      Ya, joking aside, I totally agree. MS is trying to answer with live.com. Tit for tat. Currently its not as good, but give it a few product cycles ( The 'satelite' view for maps is already better then google for places where they have taken aerial photography). That's the beauty of being the copy cat, the goal is very certain.
      A similiar example might be Japanese and American carmakers.
      Microsoft defintion of innovation is standing on top of what other people have done, and let's face it, that business practice works

  10. NT by DrSkwid · · Score: 4, Interesting

    NT stand for Nested Task, it's a register in the 286 that helps preepmtive multi-tasking which is the feature of both OS/2 and NT that distinguishes them from Window 3.x/9x that used co-operative multi-tasking.

    http://pdos.csail.mit.edu/6.828/2006/readings/i386 /s04_01.htm

    4.1.1 Systems Flags
    The systems flags of the EFLAGS register control I/O, maskable interrupts, debugging, task switching, and enabling of virtual 8086 execution in a protected, multitasking environment. These flags are highlighted in Figure 4-1 .

    NT (Nested Task, bit 14)
            The processor uses the nested task flag to control chaining of interrupted and called tasks. NT influences the operation of the IRET instruction .

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    1. Re:NT by MLopat · · Score: 2, Interesting

      NT as in Windows NT has always stood for "New Technology". In fact, the operating system at one time was simply going to be branded "NT" except that Northern Telecom (Nortel) had something to say about it.

    2. Re:NT by pla · · Score: 4, Interesting

      NT stand for Nested Task

      Or, officially, "New Technology".

      Or, the most likely of all, by analogy to IBM -> HAL (as in, HAL-9000 from the movie 2001: A Space Odyssey), VMS -> W(indows)NT. I would normally consider that a cute coincidence, if they didn't share Dave Cutler as a lead designer on both projects.

      But given that he did help design both OSs, and the propensity for geeks to come up with bizarrely convoluted acronyms, I'd call that the "right" answer as to the origins of the name "NT".

    3. Re:NT by lseltzer · · Score: 1

      >> NT stand for Nested Task, it's a register in the 286 that helps preepmtive multi-tasking which is the feature of both OS/2 and NT that distinguishes them from Window 3.x/9x that used co-operative multi-tasking.

      As others have said, NT of course stands for "New Technology" and is a marketing term, not a reference to a bit flag in a register.

      And Windows 9x preemtively multitasks.

    4. Re:NT by Epicyon · · Score: 1
      While NT may in fact stand for Nested Task, that may not be the origin of the use of NT in Windows NT.

      "In the fall of 1988, Microsoft hired David N. Cutler ("Dave") to lead a new software development effort: to create Microsof's operating system for the 1990's. Dave, a well-known architect of minicomputer systems, quickly assembled a team of engineers to design Microsoft's new technology (NT) operating system." (Custer 1993 p2)

      (Finally vindicated for moving this book around with me all over the country for the past 13 years when it has almost zero relevance today.)

      It's interesting to note the design goals of the system: Extensibility, portability (including a modular structure), reliability and robustness, multiprocessing and scalability, distributed computing, POSIX compiance, Government-certifiable security

      When I first read through this book, I was exited by the goals and looked forward to seeing the evolution of the OS. Even now, many disillusioned years laters, I believe Microsoft set out to create an exemplary product. It seems likely that Microsoft lost their way. (IE is integrated into, and cannot be abstracted from, the OS,etc.) Accomodations kept being made to fulfill market (or marketing's) demands which slowly eroded the fundamental goals of NT's original development resulting in the nearly unmanageable behemoth we're faced with today.

      Custer, H. (1993). Inside Windows NT. Redmond, WA: Microsoft Press.

    5. Re:NT by diegocgteleline.es · · Score: 5, Interesting

      Sight. This topic. Again.

      Just check the Windows NT wikipedia page, which links at page, where you can find this quote from one of the original NT creators:

      "We checked the first code pieces in around mid-December 1988," Lucovsky said, "and had a very basic system kind of booting on a simulator of the Intel i860 (which was codenamed "N-Ten") by January." In fact, this is where NT actually got its name, Lucovsky revealed, adding that the "new technology" moniker was added after the fact in a rare spurt of product marketing by the original NT team members. "Originally, we were targeting NT to the Intel i860, a RISC processor that was horribly behind schedule. Because we didn't have any i860 machines in-house to test on, we used an i860 simulator. That's why we called it NT, because it worked on the 'N-Ten.'"

      So please, stop all those theories, the origins of the name are well documented.

    6. Re:NT by fa2k · · Score: 1

      preepmtive multi-tasking which is the feature of both OS/2 and NT that distinguishes them from Window 3.x/9x that used co-operative multi-tasking.

      Windows 9x did support preemptive multitasking to an extent. The NT-flag/IRET point still is correct, but I must assume that the NT flag was used in Windows 9x too.

      From http://en.wikipedia.org/wiki/Pre-emptive_multitask ing:
      Windows 95 and 98 only pre-emptively multitask if the running software is capable of dealing with pre-emptive multitasking. Much of it is not. Even tasks which are part of the operating system (eg updating graphics and window displays) are often adversely affected by programs which "busy wait".
    7. Re:NT by dryeo · · Score: 1

      Except NT started out as OS/2 NT v3. I have a Byte around here with a little news blurb about MS actually booting up OS/2 NT v3 for the first time. This was on a MIPS processor IIRC.

      --
      https://en.wikipedia.org/wiki/Inverted_totalitarianism
    8. Re:NT by man_of_mr_e · · Score: 1, Interesting

      Actually, no. "New Technology" was actually the second name of the code name. It was originally derived from the first CPU they wrote NT for, the Intel N-Ten, which eventually became the i860 Risc CPU.

      When they ported NT to x86, they changed the name to "new technology", then later claimed it didn't stand for anything anymore (because it's harder to trademark an acronym).

    9. Re:NT by siride · · Score: 1

      The NT is not used (or irrelevant) because modern OSes like Linux and Windows NT do not use the x86 task management mechanism. Rather, tasks and task swapping are implemented in the kernel by saving and restoring register manually. Furthermore, all interrupts use interrupt gates instead of task gates, so no x86 task switching occurs there either. On both Linux and Windows, the double fault exception, however, does use a task gate, probably to avoid any further faults which would reset the processor.

    10. Re:NT by AJWM · · Score: 1

      the origins of the name are well documented.

      Sorry, the recollections of an involved party long after the fact do not constitute "well documented". Show me the contemporaneous emails or memos, that's documentation.

      I can't imagine why anyone would make up a story like the "N-Ten" story (although who writes it "N-Ten" rather than "N10"? Calling it Windows NIO (or Neo?) would make more sense), but what you quote does not constitute "well documented".

      --
      -- Alastair
    11. Re:NT by DECS · · Score: 1

      TFA actually pointed out the NT name is said to come from i860, and also mentions the use of NT in OS/2 3.0. Both were ~1988, so we don't need wikipedia in 2006 telling us trivia.

      Recall that the Wikipedia is hardly well sourced. Many tech articles are supported by sensationalist articles from the Register which are "original research," or in other words conjecture designed to be snappy used as supporting facts.

      Compare the wikipedia article on the iPod and the Zune. The iPod article scrounges up criticisms from every corner of Wikipedia, while the Zune reads like Microsoft talking points presentation. Pretty much every Microsoft article is a glowing fanfest, with little or no criticism at all. All their vaporware products aren't even mentioned, despite there being 4-5 titles every year that could be articles. Compare the apology of an article on Cairo. Misses completely.

      Other Apple articles are just as bad, and read like a copy paste job from the web, not a set of facts with any historical significance.

      The wikipedia is pretty useful outside of tech, but its tech articles are full of advocacy and reflect the same subjective bias of other user generated content. Articles skirt anything of encyclopedic value to present trivia, much of which is made up crap.

      I know this because I've tried to write the beginnings of useful articles; what's already there is just ads and populist fiction. Who reading the wikipedia cares what the Apple store sells!? We don't need wikipedia telling us up to date reports of what's on sale on another web page, but a little history or background on the apple store as a project might be useful or interesting.

    12. Re:NT by drsmithy · · Score: 1

      (IE is integrated into, and cannot be abstracted from, the OS,etc.)

      Bollocks.

      Do not confuse the lack of a retail product sans IE, with IE not be modular. Business and marketing != software engineering.

      NT seems to have met its design goals quite well. That you can't personally build yourself a patchwork quilt of an OS based on it like you can with Linux, is a business decision, not a technical limitation.

    13. Re:NT by drsmithy · · Score: 1

      NT stand for Nested Task, it's a register in the 286 that helps preepmtive multi-tasking which is the feature of both OS/2 and NT that distinguishes them from Window 3.x/9x that used co-operative multi-tasking.

      This would be more convincing if there had ever been even the slightest hint that NT would ever have been targeted at the 286.

    14. Re:NT by MLopat · · Score: 1

      Were you on the team? Or did you simply read the misleading wikipedia article?

    15. Re:NT by Epicyon · · Score: 1
      My point refers to the statements Microsoft had made during the antitrust hearings regarding the fact that IE was an integral component of Windows and could not be removed.

      Microsoft stated that the merging of Microsoft Windows and Internet Explorer was the result of innovation and competition, and that the two were now the same product and were inextricably linked together and that consumers were now getting all the benefits of IE for free.

      A number of videotapes were submitted as evidence by Microsoft during the trial, including one that demonstrated that removing Internet Explorer from Microsoft Windows caused slowdowns and malfunctions in Windows. Although I completely agree that marketing != software engineering:

      Because of the limited nature of POSIX.1, the POSIX subsystem on Windows NT does not provide any support for networking or system security. Many people feel that the inclusion of the POSIX subsytem was really a marketing ploy to increase NT's market penetration. http://en.wikipedia.org/wiki/United_States_v._Micr osoft http://scilnet.fortlewis.edu/tech/NT-Server/archit ecture.htm
    16. Re:NT by man_of_mr_e · · Score: 1

      No, I wasn't on the team, but I did read interviews with both Mark Lucovsky and Dave Cutler where they both mentioned this. The Wikipedia article is accurate.

      http://www.winsupersite.com/reviews/winserver2k3_g old1.asp

      "Finally, it was time to start writing some code. "We checked the first code pieces in around mid-December 1988," Lucovsky said, "and had a very basic system kind of booting on a simulator of the Intel i860 (which was codenamed "N-Ten") by January." In fact, this is where NT actually got its name, Lucovsky revealed, adding that the "new technology" moniker was added after the fact in a rare spurt of product marketing by the original NT team members."

      And in case you don't trust Paul Thurrott, here's slides from one of Locovsky's presentations:

      http://www.usenix.org/events/usenix-win2000/invite dtalks/lucovsky_html/tsld006.htm

    17. Re:NT by drsmithy · · Score: 1

      My point refers to the statements Microsoft had made during the antitrust hearings regarding the fact that IE was an integral component of Windows and could not be removed.

      This is a wholly separate issue from IE being modular from a software engineering perspective.

  11. building a custom bike/car by stock · · Score: 1

    Vista should be compared with the construction of
    a custom build bike/car to be displayed at Detroit's Autorama
    and hopefully will draw the last 8 cut.
    Well it might make the best 8, but Vista will never be
    a winner in real day practice, because no-one is going to
    drive a $1 million cost custom to the supermarket or even
    to the next state or cross country.

    Vista is not the next industry desktop workhorse,
    certainly not of what i have seen. Being the biggest bad ass
    ballmie bully on the block might pull it through, but
    it won't make much friends.

    1. Re:building a custom bike/car by Anonymous Coward · · Score: 0

      I don't know if it's really like a custom bike or car. It is intended to be a mass-market product. It may not be cheap, but imagine how much more it would cost if Microsoft only intended to sell one copy? The buyer would have to pay for all the development and testing - many billions of dollars, I expect.

      Vista is not the next industry desktop workhorse, certainly not of what i have seen. Being the biggest bad ass ballmie bully on the block might pull it through, but it won't make much friends.

      I think it is. It will end up on every corporate desktop because it'll be hard to buy new machines without it. Upgrades will involve upgrading to Vista. Similarly, it'll end up on many home computers because it will be preinstalled by the OEM. It'll take a few years, but eventually it will be almost everywhere.

      There's a pattern here. This is why XP was successful, too, even though it added little to Win2K.

  12. Better Windows history here... by Aphrika · · Score: 5, Informative

    Wikipedia - generally a little more authoritative than a (rather opinionated and flawed) blog entry.

    Incidentally, I distinctly remember Cairo not being vaporware or a hoax as stated in the article, there were certainly dodgy builds of it floating around before it was canned and NT 4.0 appeared as a Win95-ified NT 3.51 replacement. The idea that Cairo was a hoax in a non-starter. That's like saying Copland was a hoax, no, sometimes projects get shelved because they're not working out - OS design is an area of computing where it's incredibly easy to be idealogical about features, then figure out that you just can't deliver the goods.

    1. Re:Better Windows history here... by lseltzer · · Score: 1

      I followed all of this very carefully at the time. Microsoft was always careful to call Cairo a "set of technologies" and not necessarily a specific version that would be released at some specific point. Almost all of what they promised for Cairo did come true except for the "object-oriented file system."

    2. Re:Better Windows history here... by PsychicX · · Score: 1

      Parent is right, this article is just...bitter.

      Vista is Cairo. As is Win2K, and Active Directory, and Exchange, and SQL Server, and god knows how many other technologies out of that company. It dissolved out of product status long ago, but the overarching goals are really what have driven Windows and related development for close to 15 years. Vista was a badly executed push towards that same ideal. That "information at your fingertips" motto has controlled Windows development. Just look at the sheer prevalence of search in Vista. (Some people will want to bring up Apple's Spotlight here. Yes, they are extremely similar. Vista's version existed internally for a long time, though. Things like this tend to come up independently in multiple companies around the same time.)

      Back to the point, this article is a mess. The starting premise, though he tries to hide it, is that Vista is bad mmkay. Everything else is built backwards from there. That's why everything else is so akwardly set up and the connections are so tenuous. He's justifying his own baseless anti-Vista sentiment; the Cairo thing is just a distraction. (And let's face it, there's enough real problems with Vista that this straw man is just sad.)

    3. Re:Better Windows history here... by smallguy78 · · Score: 1

      http://channel9.msdn.com/ShowForum.aspx?ForumID=14 &TagID=83

      Plenty of information there, the Dave Probert videos cover the history pretty well if I remember right, including giving the real background of the use of NT instead of "NT stands for Nice Titties" theories and so on.

      --
      Nothing costs nothing
    4. Re:Better Windows history here... by SmurfButcher+Bob · · Score: 4, Informative

      Actually, I'd suggest that you missed the author's point, entirely. Perhaps it is due to you not being in the position to buy the various products at the time, I don't know.

      Here's the perspective. It has zero to do with "15 years later, we have a feature". It has *everything* to do with, "15 years ago, when we needed a solution, Microsoft said they would provide it in a TIMELY fashion." As a result, purchase decisions were directly impacted.

      We needed a mutlitasking OS to replace a DG Mini. Windows 1.0 was reputed to provide this functionality.
      We called them. "Multi tasking?" "Yes." "Multiple users?" "Absolutely."
      We bought it.
      They lied.
      We called them back.
      "The sales engineer was confused with the next version." End Quote.

      The project was shelved.
      CDOS, released by a company named "Digital Research", became viable.
      The project was rehashed, but Windows 2.0 was out. It's DOS support had few caveats, compared to CDOS.
      We called Microsoft.
      "Multitasking?"
      "Yep!"
      "You said the other one was. It wasn't."
      "We've totally rewritten it. It works for real."
      "Multi user?"

      We bought it.
      They lied.
      We called them back.
      "It doesn't work."
      "No? The NEXT one will, and it's due soon."

      See the pattern yet?
      We eventually bought CDOS (and later, CCDOS, a value-add version).

      We also bought Win30. Hazard a guess why?
      They lied, again.
      We also bought Win31. THAT one was initially stated to be preemptive, remember? And the sales pigs all claimed it was, when it was time to sign the check. Perhaps you've forgotten the RAGING DEBATES over that very issue, at the time... "Preemptive!" "No, it isn't!" "Yes, it is!" "No, it isn't!"

      Our project was fairly simple - run a couple of DOS boxes, and redirect STDIO to a serial port so that two people could run a program. This specific detail was explained to "Microsoft", EACH TIME.

      Every time... EVERY time... the MS tactic was to stall our purchase of a competing, fully viable product, via the gross misrepresentation of their own.

      The MS philosophy is, and has been, that it is better to ship an "empty box" on-time than to ship a working product a day late.
      And they have done so, and I have the disks to prove it - Excel's initial "DMF" floppy distribution, who's lzexpand didn't comprehend DMF... they literally put the "standard" Win31 lzex onto disk 1. Funny, it's LZEx that needs to READ these FATless disks. It couldn't POSSIBLY work. But, the version they needed wasn't read yet, so... ship it! ...To NT BO4.5, which contained such setup.ini script error gems such as "Syntax error line xxx: ***REMEMBER TO FINISH SQL INSTALL SCRIPT". I'm NOT joking. And, you don't know the half of the extent of this.

      Clearly, two "top tier" products at the time, and the installations not even been tested. Not once. NOT ONCE. And, the devs KNEW the crap wasn't finished. The Mgt KNEW the crap wasn't finished. Both cases, which were a year apart... the "official" MS reason for issuing new disks to me?

      "Media Defect". Again, I am NOT joking. Both cases, no matter how hard I argued, the call takers flat out REFUSED to admit the actual flaw. "No, the media is perfect. The setups are WRONG. Syntax errors... referencing a directory path that doesn't exist on the CD... trivial little things like that..."

      Because, you know, the standalone install disk for Exchange had the base directory in the root. On BO4.5, the base setup was a subdirectory. And the scripts hadn't been adapted for it.

      Trivial, little things. Right? Or, an omnipresent pattern, that just keeps on recurring.

      The point of the article is exactly correct; promise vaporware as a solution NOW, to prevent or stall the purchase of an existing solution, NOW. That they *might* actually deliver the vapor in five years? Irrelevent; I am NOT going to buy a "viable" solution today, when "nervana" is coming next week. I will wait, so that I can assess. Or worse, if the "vapor" is claimed to now exist,

      --

      help me i've cloned myself and can't remember which one I am

    5. Re:Better Windows history here... by master_p · · Score: 1

      Well, if you and your company buy products based only on what the sales guy says on the phone, then I have a really good ranch for sale right in the middle of Manhattan...

      (seriously: you did not even wait for the magazine reviews?)

    6. Re:Better Windows history here... by Tony-A · · Score: 1

      It is said that if we fail to learn from history, we are destined to repeat it.
      Methinks we don't learn very well.

  13. More spam from Daniel Eran by Anonymous Coward · · Score: 0, Informative

    More spam from the idiot who was caught spamming digg.

    This guy has been caught spamming dozens of sites. Apparently, only /. editors don't get it.

    1. Re:More spam from Daniel Eran by RFaulder · · Score: 0

      If he were trying to be a legitimate writer - and some of his articles are genuinely interesting - then what would he have to gain by making such an elaborate scheme of spamming? I don't buy it.

    2. Re:More spam from Daniel Eran by Anonymous Coward · · Score: 0

      He is an attention whore. He calls his blog a "magazine" and then spams links to it everywhere he can find. From previous comments it looks like he has stumbled on usenet now. I can only assume that he is finding himself banned from more and more of the places that he used to use to drive traffic to his site.

    3. Re:More spam from Daniel Eran by Siker · · Score: 1

      I'm not fully aware of the specifics but you should probably provide both sides of the story. The response to that claim was that the users registered when Mr. Eran was writing about Digg and requested his readers to give him a hand. So supposedly there is a number of legitimate users who came in from his blog and registered for the express purpose of only digging the articles they liked from Roughly Drafted.

      I'm not taking a stand in the question but just pointing out there are two sides to every story.

    4. Re:More spam from Daniel Eran by Anonymous Coward · · Score: 0

      Well that is because Mike Caddick, aka Lackawack, aka Zybch (and other alieses) has made it his life's work to write to every site that has ever posted an article from RDM and spun his tale of DE being a "spammer" and manipulating Digg.

      I have not only gotten Mike's emails, but have talked to other webhosts who got the same thing. What is most interesting is that generally clueful people are so quick to fall for his bullshit hatemail and the anonymous web troll sites he sets up. As if lots of truth gets whispered around by anonymous trolls. WTF?

      Why does Mike Caddick care what DE writes about? DE likes attention for the stuff he writes, but he doesn't send out bulk emails - I've seen postings in two Mac newsgroups with a link and an article blurb, and I've seen his stuff posted to the front page of Digg and Slashdot. Is the world falling down? Even if you don't agree with his ideas, at least he writes in an interesting way that gives people something to talk and think about.

  14. This article is barely coherent by defile · · Score: 2, Insightful

    Factual errors aside, I think he's trying to say:

    Microsoft announced it had big things in development, didn't quite release all of the things they announced. This is fraud. Microsoft bad. They did it on purpose, by design. We're onto you guys, you won't fool us with Vista!

    He references The Mythical Man-Month as if this would give him some kind of software development street cred. I don't buy it, mainly because he doesn't seem to have ever been involved with any software development project.

    Many software projects start with ambitious and optimistic sets of features. And by many, I mean all. The bigger the project, the more ambitious the scope. "Yeah! Our next generation Operating System is going to have an OBJECT FILE SYSTEM and DISTRIBUTED COMPONENTS and JUST IN TIME COMPILATION and ADAPTIVE HEALING and ADVANCED AI COMMAND INTERFACE and VOICE RECOGNITION. The future is NOW! We're awesome!" Developers believe the hype and do a lot to generate it. And if they believe it, and they're implementing the fucking thing, what chance do marketers have of looking at it critically? None. So they tow the line.

    Result? The ambitious wildly impractical story is impossible to keep quiet. Sure, you can certainly fault companies for announcing features well before they're release candidate quality, but ambitious features getting cut because project deadlines are slipping happens all the time. Aside from the bad press that's generated from missing your release date, and the investment you blew developing features which don't get commercialized, there aren't many other downsides. If you can afford it, who cares?

    I can totally imagine cutting these features if I were the project manager and we missed our release date; the decision process would go something like this: what is the most expensive feature we're developing right now that has the lowest return on investment that if we cut, would allow us to release much earlier? "Object filesystem" probably makes the top of everyone's list. It gets cut it in a heartbeat. What, was marketing hyping the shit out of it this whole time? I hadn't noticed, because I haven't left my cubicle in 36 months. Tough it out, marketing clowns.

    1. Re:This article is barely coherent by julesh · · Score: 1

      Factual errors aside...

      Actually, factual errors not aside. This is a most peculiar piece of writing I've seen for a while. It ignores the popular myths about how Windows NT came to be, and cuts straight for the truth... then neatly sidesteps it and comes to incorrect conclusions. It's almost like it's been written by somebody who knows the real story as a deliberate disinformation piece. But who'd do that?

      From the article:
      Microsoft initially targeted NT to run on the i860, Intel's new 64-bit RISC processor that was supposed to usher in the future.

      The i860 was a 32-bit processor. If it were a 64-bit machine, MS would have struggled to downport NT to 32-bit architectures after initially developing the kernel on it.

      Of course, Microsoft and IBM had also long referred to OS/2 3.0 as "NT," for new technology, so the idea behind the i860 as the source of NT's name might be historical revisionism.

      Windows NT development started out as OS/2 3.0 development, and was switched to be in the Windows line later when Win3.0 took off. You'd have thought the writer could figure that maybe, perhaps, the i860 kernel that Cutler wrote for NT was originally slated to be for OS/2, and that perhaps therefore OS/2 3.0 was targetted at the i860 as well?

      Not saying that this *is* the true meaning behind the NT name, but it's more likely than the "new technology" thing, which is widely regarded as a marketing-inspired backformation. Interestingly, he has used exactly the right argument here that dispels the "WNT=VMS+1" theory, but he doesn't mention that one.

      Xenix eventually turned into today's SCO UNIX.

      SCO don't sell a product called "UNIX". SCO OpenServer is what used to be called Xenix. "SCO UNIX" is likely to be confused with "SCO Unixware", which is an entirely different product line, originally developed by Novell.

      Despite quaint stories about Bill Gates singlehandedly writing DOS on the back of a napkin

      Anyone heard these stories? The much more common one is that he was in a hurry for an operating system so bought it form its original author for some pittance or other. That's very commonly known.

      Windows 3.0, a DOS application

      ??? Windows 3 was somewhat more than an application. In almost all ways it qualifies as an operating system (it only lacked a device driver framework, relying on DOS to provide that in its place). But the writer's thesis doesn't work if Windows 3 was an operating system, so it's an application instead. Yeah, right.

      At some future point, the world was supposed to trade in the essentially free-to-obtain DOS with a paid $200 copy of OS/2. That would enable PC users to run the software designed for DOS and Windows they already could run, as well as new software native to OS/2 that they did not have and did not yet exist. Hmm.

      It's amazing that neither IBM nor Microsoft seemed to worry that this strategy might not work out, but everything is much clearer in hindsight.


      Perhaps because that was never anybody's strategy. Nobody expected people to switch to OS/2 for no reason. Windows was a portability thing: if the Windows API were supported on both DOS and OS/2, then applications could be written that targetted either. When people came to buy a new computer, they could see that the more advanced operating system basis of OS/2 could give them superior performance to DOS, and so buy OS/2 instead.

      Also, DOS wasn't "nearly free to obtain". I distinctly remember paying £70 for a copy back around the time we're talking about, which makes it pretty similarly priced to the $200 claimed for OS/2.

      a world ready to believe that everything Microsoft could plan would be delivered at some point, even though Microsoft had absolutely no history of delivering any significant or original operating system technology.

      Other than, you know, DOS and Windows. And this MS who had recently hired Dave Cutler, a very respected OS engineer

    2. Re:This article is barely coherent by DECS · · Score: 1

      The i860 was a 32-bit ALU along with a 64-bit FPU. All of its buses were 64-bits wide, or wider. But lets ask Intel: the Intel i860 64-Bit Microprocessor Data Sheet.

      You pick out various other things out of context to discredit my article, but you are clearly just excited about Microsoft. The very real problem is that this article directly attacks the church you worship at; its not a personal thing, I just think you shouldn't be worshiping mediocrity.

      It's simply undebatable that Microsoft promised Cairo in 1991 as its own NeXT that would arrive just a few years later, and then spent the 90's cranking out more procedural DOS instead. If you are impressed with Microsoft's track record, its only because you don't know what would be possible had they not stopped any and all real progress.

      If you want to call a mix of fraud and incompetence "optimism," well maybe you should work for the government.

      -

      The Register's Collapsing iTunes Store Myth

    3. Re:This article is barely coherent by julesh · · Score: 1

      The i860 was a 32-bit ALU along with a 64-bit FPU. All of its buses were 64-bits wide, or wider.

      The same was true of the Pentium. That doesn't make the Pentium a 64-bit processor.

      But lets ask Intel: the Intel i860 64-Bit Microprocessor Data Sheet.

      Marketing bullshit. Intels engineers knew at the time that they weren't producing a 64-bit processor. But there were 64 bit aspects to it, particularly WRT its SIMD capability of working on two 32 bit words with the same instruction. Its ALU was 32 bits, though, as was its address generation. Pointers held in registers are held in 32 bit registers. By modern definitions of a 64 bit processor, the i860 wasn't one of them. I'll let the source code for gcc's output module for it speak: /* Width of a word, in units (bytes). */
      #define UNITS_PER_WORD 4

      That's a 32 bit processor, there.

      you are clearly just excited about Microsoft

      Hardly. Out of personal choice, I'm a Linux user. My opinion is that the world would be a better place if MS had never got into the operating systems market. But that doesn't mean I'm willing to let inaccurate criticism of them pass. Criticise MS for their monopolistic practices. Criticise them for pushing the Win95 family on people despite it being total shit. Criticise them for producing bloated monsters that need ever more and more resources to run. Criticise them for consistently releasing products late. Criticise them for their FUD. Criticise them for failing to release API information and complete protocol documentation. Criticise them for dumbing down their systems to the point where they actually become harder to use in the name of simplicity. But don't criticise them for something that's untrue. I'm convinced that the claims they made about features they planned for Cairo were honest. Just like the features they announced for Longhorn were. They were ambitious, and they were optimistic in their announcements. They failed to deliver. This isn't unusual; most tech companies do this. Apple is very much an exception here, in that they keep details of their new products under careful wraps until just before launch. Few others do this, so don't criticise MS for following the majority.

    4. Re:This article is barely coherent by DECS · · Score: 0, Troll

      Quibbling about whether the i860 fits your idea of what 64-bit means is not very interesting. I was only pointing out that the i860 was a modern processor. I made no error.

      Clearly, you can write for days about how you don't like things. Just don't confuse your personal prejudices against reality and "factual errors."

      I didn't present that Microsoft's Cairo was bad only because it didn't achieve everything it hoped; rather, I pointed out that Microsoft has a history of overpromising and underdelivering.

      In 1981, 1991, and 2001, Microsoft promised to deliver what other companies actually delivered within a few years... except that Microsoft didn't really ever deliver.

      Its version of the 1984 Mac came out in the end of 1995 - unimpressively.
      Its version of the 1989 NeXTSTEP stopped trying to ship in 1996.
      Its version of the 2002 Mac OS X is just now planning to ship in 2007, minus most of its planned features.

      The real question is: why are you defending the world from reality?

      And before you completely spaz out about how little I like Microsoft, remember that I have repeatedly castigated Apple for its failures as well.

      Why Apple Failed
      Newton Lessons

      I make errors as well, and appreciate when they are pointed out so I don't make them again, but your rant just pulls crap out of context and presents it in a very disingenous and misleading way. You aren't attacking facts, you're just trying to attack me personally because there is nothing really controversial about Microsoft's reign of incompetence over the tech industry.

    5. Re:This article is barely coherent by julesh · · Score: 1

      Its version of the 1984 Mac came out in the end of 1995 - unimpressively.

      When was the last time you used an 84 Mac? The original Mac OS was single tasking, only supported monochrome displays, allowed no network connectivity, and didn't support heirarchical filesystems. Its memory accesses were limited to 1MB, I believe. Windows 2.0, released in 1987, was superior in most respects, and an equal in many respects to much later versions. MacOS's multitasking capabilities didn't match Windows 2.0 until the release of System 7 in '91. MacOS wasn't an equal of the features in Win95 until the first release of OSX in 99. And I'll admit that that was a far superior OS to anything MS had released then, or had in the pipeline.

      So, basically, in terms of essential features like multitasking, memory protection and virtual memory support, MacOS has lagged behind Windows consistently. All Apple had first was a good user interface.

      But go ahead and believe that Apple led the way if you want.

      Its version of the 1989 NeXTSTEP stopped trying to ship in 1996.

      Almost all of the features MS had discussed as NeXT competitors shipped in NT4 in 1997. Primarily, we're talking about DCOM. Note that the NeXT of 1989 was targetted to high end workstations, while Windows NT was targetted primarily to top-end PCs, which lacked power and features compared to the workstations of the day. That it lagged behind somewhat is only to be expected.

      Its version of the 2002 Mac OS X is just now planning to ship in 2007, minus most of its planned features.

      Well, actually, no. First, it has already shipped, just not to retail markets. Second, the features that were abandoned (WinFS and NGSCB being the only two anyone seems to talk about) don't really count as "most". There are significant numbers of new features that did make it, most notably the Aero UI, the Avalon API, XAML, and several new built-in applications. Yes, MS are playing catchup to Apple here. But "minus most of its planned features" is just plain wrong.

      why are you defending the world from reality?

      Because your version of reality seems to be warped and twisted, and connected only obliquely with the real world.

    6. Re:This article is barely coherent by DECS · · Score: 1

      When you say things like Windows 2.0 was technically impressive product, it makes it hard to take you seriously.

      If you pull out bullet points from Wikipedia, then it appears that MS delivered some interesting innovations. Except they didn't; it was all crap. Nobody bought Windows 2.0. That's why MS was working on OS/2 until 1990.

      Multitasking, PEM and PM sound great, but they didn't really work in Win95 when running actual applications people had. It wasn't more stable and reliable than the "ancient" Mac OS.

      Further, I presented Microsoft's history with Cairo as a lesson about Microsoft, not in direct comparison with Apple. It's not an Apple vs MS holy war. I presented similar histories of Apple's failure to deliver their own products (linked to from TFA).

      If you leave Apple out of the picture, it gets even worse for Microsoft, because other vendors were offering the features of Cairo long before MS even missed its first several ship dates.

      NT 4 did not ship with all the promises of Cairo; Ms only managed to deliver its own version of PDO five years late, and 2-3 years later than NeXT had delivered its Windows port!

      Don't ask me to give NT a break because it was trying to run on "high end PCs" rather than "workstations," because NeXT stopped building its own hardware and was running on PCs as early as 1992. That's FIVE YEARS before NT 4 shipped.

      "My version" of reality only seems "warped and twisted" because you're reading history from Wikipedia without criticism or historical reference.

      The Secrets of Pink, Taligent and Copland (and OpenStep)

    7. Re:This article is barely coherent by julesh · · Score: 1

      When you say things like Windows 2.0 was technically impressive product, it makes it hard to take you seriously.

      Did I say that? No; I said that in a number of important ways it was superior to what Apple were doing 3 years earlier, and that in many of these respects it took Apple a while to catch up.

  15. Text of TFA - Slashdotted by soulsteal · · Score: 3

    1990-1995: Microsoft's Yellow Road to Cairo
    Along with Ashton-Tate and Lotus Development, Microsoft was considered one of the Big Three software developers of the 80s. Apple courted all three to develop software for its new Macintosh.

    Ashton-Tate managed to run itself out of business, and Lotus was eventually bought up by IBM in 1995, leaving Microsoft as one of the largest and most influential developers of desktop applications.

    Microsoft's position as a vendor for both DOS and office applications gave it certain advantages over its rivals, particularly when Windows 95 appeared and obsolesced not just previous versions of DOS and Windows, but also competing developers' existing applications, including DOS standards WordPerfect and Lotus 1-2-3.

    Rapid advancements in technology created a wildly chaotic market, where simple announcements of future plans could trump real products. Given the prevalence of misinformation wars in the tech industry, it's no surprise that Microsoft applied its vast market power to become one of the most notorious sources of FUD and vaporware.

    Innovations in Vaporware
    Previous articles have considered Microsoft's vaporware attacks on QuickTime and the Newton and PenPoint OS.

    While many companies in the competitive tech field announced products they were ultimately unable to deliver, Microsoft applied an innovative, two handed approach to playing the vaporware game.

    Rather than just bluffing its hand like other companies, Microsoft played the game with a set of cards in one hand, while waving the illusion of another set of cards in the other hand. The fake set of cards were highly distracting because they looked like a much better hand than anyone else could possibly have.

    Standing around the card table were a number of analysts who all expressed how impressed they were by the cards Microsoft waved in the air, and made regular remarks about how foolish it would be for anyone else to stay in the game. The worst part was that many of those analysts could see Microsoft's real hand, and knew the company was bluffing.

    Microsoft's NT Plans Prior to Cairo
    In 1991, Apple was releasing the Mac System 7 and Tim Berners-Lee was using his NeXT to build the world's first web server and browser.

    PCs were still using the character based DOS in a slightly faster version than was released a decade earlier in 1981, although Windows 3.0 was beginning to provide DOS PC users with a rough approximation of Apple's graphical desktop.

    After witnessing sales of Windows 3.0 take off, Microsoft began its schism with IBM over OS/2 3.0 development. Microsoft's new plan involved an entirely new operating system based on its contributions to OS/2; the new OS was referred to as Windows NT.

    Unlike the existing DOS based Windows 3.0, NT aimed at being entirely new and modern in every respect, untied to DOS or to the existing x86 PC architecture.

    Microsoft initially targeted NT to run on the i860, Intel's new 64-bit RISC processor that was supposed to usher in the future. The i860 was a modern design and carried none of the legacy baggage of the standard x86 based PC.

    It included graphics acceleration features similar in principle to the forthcoming PowerPC Altivec and Pentium MMX; those features resulted in the i860 being used by NeXT to power its high end NeXTDimension video card.

    Unfortunately, the i860 didn't work out for Microsoft. All that remained from its efforts to build a new operating system based on the processor was the i860's code name: N10, which is widely repeated to be the meaning of NT. Of course, Microsoft and IBM had also long referred to OS/2 3.0 as "NT," for new technology, so the idea behind the i860 as the source of NT's name might be historical revisionism.

    No Operating System Experience
    Microsoft struggled with the complex reality of building its own operating system without IBM. Up to that point, Microsoft had only been delivering tepid updates to MS-DOS, which it had licensed from a small

    1. Re:Text of TFA - Slashdotted by anss123 · · Score: 1

      I had never heard of Cario when I got Win95 for the first time. OS/2 was just some mystical other OS that I heard was better than Win95, while AmigaOS and MacOS was those slow clunky UI that was on 'the way out'. As I 'Joe User' back then I didn't care in the least that there were better alternate operating systems out there, and I doubt 'Joe User' cares much more about operating systems these days. Point is, I think you are exaggerating the effect of Microsoft's FUDing. MS won by default, they just had to show up.

    2. Re:Text of TFA - Slashdotted by wangmaster · · Score: 1

      The problem with your line of reasoning that Cairo didn't matter is that Cairo wasn't technology that a user would really care about. By your own admission you were a 'Joe User'. Cairo kept the people who should have cared (product managers, software engineers, industry analysists, etc) dangling just long enough for microsoft to ensure their dominance in the market.

      As an OS/2 and NeXT user in the early to mid 90s I remember the cairo fiasco and it absolutely was not a case where MS just had to show up.

      Win 16->Win 32 time was definitely a make it or break it timeframe for Microsoft. At that point, there were a number of competitors that could have broken through and basically decimated Microsoft. There was alot of poor marketting on the part of those competitors at fault of course (While IBM developed a far superior product with OS/2 they really really couldn't market to anyone other than their core business market, and even then only for niche applications).

      Cairo was a huge a deal. It was the virtual carrot that kept people sticking to Microsoft waiting for the next best thing rather than retool and adopt a competitor's platform. The ironic thing is, Microsoft really beat IBM at their own game considering it was IBM that developed the tactic of FUD :)

    3. Re:Text of TFA - Slashdotted by x2A · · Score: 1

      Tellin me! "The Thing" that MS did that got me using it was to get their OS somewhere where I saw it and used it, and compared to everything else I had used at the time, it was a clear winner. "They just had to show up" covers it pretty well I think.

      I also like the articles comparisons between MS and Apple, clearly ignores things like the fact that Apple didn't make up the GUI - they sent guys over to Xerox to study and build from theirs... and then put patents on things like "overlapping windows", leaving MS with only being able to split screen until a license agreement was formed between the two.

      This is clearly a case of "I don't like MS, everyone else is good(tm), MS is bad, now let me rationalise it".

      --
      The revolution will not be televised... but it will have a page on Wikipedia
  16. Ok, I'll bite. by SanityInAnarchy · · Score: 2, Insightful

    What did Windows 95 actually add? The only thing I can think of is Win32, but really, even Microsoft seems to be admitting this isn't a lot -- they are giving away free upgrades to XP 64-bit to anyone with a legit 32-bit copy of XP Pro.

    --
    Don't thank God, thank a doctor!
    1. Re:Ok, I'll bite. by johnw · · Score: 5, Insightful

      What did Windows 95 actually add? W95 actually followed on from W3.1 rather than W3.0. The main feature which it added (and the thing which drove Microsoft to release it) was incompatibility with OS/2. Because IBM had licensed access to the W3.1 source they were able to achieve first-rate compatibility for OS/2 running W3.1 programs, plus much better stability, multi-tasking etc. A crashing W3.1 program running on OS/2 simply took itself out rather than the whole system. Microsoft saw themselves potentially losing market share in a big way, so rushed W95 out.

      This has always been the way with Microsoft. They'll happily deny there's anything wrong with a product, no matter how much evidence exists that there is. The *only* thing that will move them to act is the prospect of losing market share to a better product.
    2. Re:Ok, I'll bite. by ksalter · · Score: 1

      So you are saying that Win32, released more than a decade ago, is "not a lot" because NOW (a decade or more later) you can get a 64 bit OS for free? Puhleeeze.... Anyway, Windows 95 provided a pre-emptive multitaking OS that was backwards compatible. Of course, there were other OS at the time that had this too (Unix and OS/2, among others), but this was extremely important to the survival of Windows as an operating system. The point is that this "article" had a very weak premise and was not-objective. Why stuff like this sees the light of day is beyond me. Oh wait, it is anti-Microsoft.

    3. Re:Ok, I'll bite. by Kenshin · · Score: 1

      32-bit architecture had been around for quite a while on desktops when Win95 came around, so people were aching for the opportunity to use it.

      64-bit is still relatively new (for Intel-compatible desktops), and offers no major benefits at the moment.

      --

      Does it make you happy you're so strange?

    4. Re:Ok, I'll bite. by man_of_mr_e · · Score: 1, Insightful

      Win16 to Win32 was a huge deal. Though Win32 retained a large number of 32 bit versions of 16 bit API's that allowed developers to (largely) just recompile their apps with only about 10% or less work, there was also a significant number of new API's... more actually, than the Win16 API's.

      Win64, however, is largely just extending the Win32 API's to 64 bits and adding a few new memory management API's. So the two transitions can't really be compared.

    5. Re:Ok, I'll bite. by HairyCanary · · Score: 1

      Wasn't Win32 actually available in 3.1? It's been so long that my memory may be incorrect, but I think I remember that Freecell was available for 3.1, and in fact it was created as a demo of Win32 API usage.

      Windows 95 added the start button. Yay.

    6. Re:Ok, I'll bite. by cnettel · · Score: 4, Informative
      Win32 is not to Win16 what Win64 is to Win32. Win64 is a recompile, with a few typedefs changed and a few further changes where they were really needed.

      Win32 contained lots of changes compared to Win16. Threads, overlapping I/O, lots of new controls, additions to GDI, long file names, pipes for IPC. It might seem like a joke, but access violations really had a greater chance of not taking the full machine down in Win95, versus Win 3.1.

      And of course, a full driver model for all devices, with the Registry (yuck) to track the config. Yep, you could do anything in a VXD in 3.1, but there was no real structure to it. 32 bit disk I/O wasn't present in the original 3.1 either, so the difference is greater if we compare 3.1 versus 95, or the very last releases of 3.11 WfW versus 95.

    7. Re:Ok, I'll bite. by TheRaven64 · · Score: 4, Informative
      Win32s was available for Windows 3.1. It exposed some win32 APIs to win16 developers, but not all of them. From the Wikipedia page:

      Although ostensibly compatible with early versions of Windows NT, many functions were not implemented including threading and asynchronous I/O, newer serial port functions and many GDI extensions. This essentially limits it to applications specifically designed for the platform.
      --
      I am TheRaven on Soylent News
    8. Re:Ok, I'll bite. by julesh · · Score: 1

      What did Windows 95 actually add?

      * Preemptive multitasking
      * 32-bit flat memory model
      * Win32 API (which was a significant improvement at the time)
      * Integrated TCP/IP support, rather than relying on an optional extension
      * Increased maximum supported memory configuration to (IIRC) 256MB from 16MB
      * Desktop-oriented GUI
      * Paging rather than segment-swapping improved virtual memory performance substantially
      * Freecell

      Need I go on?

      Win95 was a huge improvement over Win3.1

    9. Re:Ok, I'll bite. by Anonymous Coward · · Score: 1, Interesting

      No, the main thing it added was full 32-bit support with process separation, threading with preemptive multitasking, virtual memory as well as kernel isolation. It was a fairly major overhaul from the DOS kernel, although much of that overhaul was under the scenes and invisible to the end user. But the result was apparent. In Win3.x a program could enter a hard loop and bring the system down because Win3.x depended on the program yielding to the OS to permit other programs to run. In Win95 that was not possible. It was an excellent middle ground between where DOS/Win3.x was and where NT was going, permitting nearly 100% backward compatibility while stabilizing the platform. It also made it abstract enough from the underlying kernel implementation to completely change the kernel out six years later with the NT kernel when good software practices made it possible to lock down the third ring, completely isolating processes from each other and the kernel, and hardware caught up reasonably enough to run the rest in emulation.

    10. Re:Ok, I'll bite. by SanityInAnarchy · · Score: 1
      Win32 API

      Someone else has pointed out that the Win32 API was available on Win3.1.

      Integrated TCP/IP support, rather than relying on an optional extension

      So what's wrong with an optional extension?

      Increased maximum supported memory configuration to (IIRC) 256MB from 16MB

      Ah, true. But then, Windows 3.1 actually ran in 16 megs. Win98 probably used 16 megs just for the OS.

      Cheapshots aside, according to Wikipedia, Win3.1 supports 386 Enhanced Mode:

      386 Enhanced mode implemented all the benefits of Standard mode, plus 32-bit addressing and paging for faster memory access, plus virtual 8086 mode for safer execution of MS-DOS programs: each of them now ran in a virtual machine.

      I don't know if that does anything about the 16 meg limit, but at the time, MS recommended 8 megs of RAM for "optimal" performance. So really, it's kind of like how XP 64-bit now supports more than 4 gigs of RAM, but notice how people aren't exactly flocking to it -- frankly, my 2 gigs is more than enough for now.

      Desktop-oriented GUI

      And how is that different than maximizing the Program Manager? I mean, there are some nice, cosmetic things, but really...

      Freecell

      Which was on the Plato -- and I believe there was a Win32 version that ran on Win3.1.

      I mean, there were improvements, but nothing really huge. Kind of like Vista right now.

      --
      Don't thank God, thank a doctor!
    11. Re:Ok, I'll bite. by NormalVisual · · Score: 1

      And the most important thing (to me, anyway) - no more segmented memory. Prior to Win32, the largest single chunk of memory that could be easily be dealt with under Windows was 64KB, and it was a royal PITA dealing with that restriction. With Win32 they didn't attempt to support anything earlier than a 80386, so you could easily use the entire flat memory space. Many, many Windows coders rejoiced.

      --
      Please stand clear of the doors, por favor mantenganse alejado de las puertas
    12. Re:Ok, I'll bite. by triso · · Score: 1

      ...It was an excellent middle ground between where DOS/Win3.x was and where NT was going, permitting nearly 100% backward compatibility while stabilizing the platform.... It was not stable enough. Any misbehaving DOS program or any buggy Win32 program being developed would bring Win 95 down faster then a two-dollar whore.

    13. Re:Ok, I'll bite. by toadlife · · Score: 1

      As the parent said, migrating their userbase to their NT based OSs, while giving them 100% backward compatibility was *the* goal of Win9x. Anything other than that was (obviously) down the list of priorities. I'm not sure what the parent meant when he said stability, but I'm thinking (s)he meant moving them all to an OS that shared the same code base.

      Moving users straight to an NT based OS would have caused backward compatibility problems, which would have discouraged users from migrating at all. Virtualizing old apps on top of NT would have caused huge performance issues due to the slowness of the hardware at the time, so that was not an acceptable solution either. Screwing customers over on backward compatibility, would have opened the door for viable competitors like Apple to move in and suck up a ton of their customers.

      Win9x did one thing it was designed to do very well. It made the move to Win9x much less painful (from a compatibility standpoint at least) than a move straight to NT. Once most people were moved over to Win32 apps, Microsoft ushered in 2000 and then XP. Of course, 2000 and XP also had backward compatibility compromises in their extremely insecure defaults. Those compromises enabled compatibility with Win32 apps written with no security in mind.

      Vista is the next step in the long migration path, as it removes the security compromises of Win2k and WinXP.

      --
      I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
    14. Re:Ok, I'll bite. by Anonymous Coward · · Score: 0

      "32 bit disk I/O wasn't present in the original 3.1 either..." It wasen't present in Win 95 either... it first came 2 or 3 years later in Win 95 OSR2.

    15. Re:Ok, I'll bite. by Anonymous Coward · · Score: 0

      The AC grandparent article was saying that a confused Windows app might never yield, and in the cooperative multitasking world of Windows 3.x that would be enough to lock up your system; in Windows 95, that could never happen. There were other ways to lock up a W95 system, of course.

      W95 was a home run. Its success was deserved.

      By the way, one other notable feature was that it gave long filenames, with spaces and upper-and-lower-case letters. It was way better than previous versions of Windows.

      And it was reasonably stable when it shipped; I worked at MS at the time, and I used W95 for about 9 months before it shipped. I remember thinking "This thing has been stable for months. Why don't they just ship it?" Of course, looking back, that was probably because my computer at MS had a lot of memory for the time (16MB or something like that). If you wanted W95 to be stable, it really really helped to give it way more memory than the "recommended minimum".

      It wasn't perfect, but I think that "two dollar whore" crack was uncalled for.

    16. Re:Ok, I'll bite. by jimicus · · Score: 1

      I had to support 120 Win9x boxes for a year. I still have the nightmares.

      Without Ghost, it was, to all intents and purposes, impossible to manage in any meaningful way. With Ghost, the only sensible way to manage it was "when in doubt, reimage first and ask questions later".

      Stable? When you see 15% of the workstations have been left logged on because a program had locked them up completely, that is not stable. Hint: Half-decent pre-emptive multi-tasking is a lot harder to bring down than that.

      Spaces and mixed case in the filenames? Give me a break, Unix had had that for years.

      "Better than previous versions of Windows" may be true, but it's like saying "Cholera is better than bubonic plague".

    17. Re:Ok, I'll bite. by Bert64 · · Score: 2, Interesting

      Your thinking of win32s...
      Ofcourse, the win32 API came first in NT3, win32s was the port of it to dos-based windows... Windows 95 was basically 3.11 with win32s bundled in, a new interface and a few other things bundled in by default. And it came bundled with dos instead of having to install it seperately.
      They both still had dos underneath, tho 95 started windows by default whereas 3.1 didn't.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    18. Re:Ok, I'll bite. by toadlife · · Score: 1

      I had to support more than that many and I agree. I'm talking student computer labs so stability wasn't really the issue. It was security. We had this hokey program called "Winsheild" which was supposed to "secure" the computers against changes, but of course it was a complete joke.

      After getting sick and tired of having to ghost the damn things every week just to keep them working, I moved the labs from Win9x to NT4 Workstation. After moving them to a NT based OS, the percentage of my time the labs took from me went from 75% to 5%. I was able to start doing more interesting and useful things with my time at work after that.

      Win9x had it purpose. It moved Windows users to NT. That's all it was good for.

      --
      I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
    19. Re:Ok, I'll bite. by rbarreira · · Score: 1

      It's funny that the parent post is moderated to 5 while this reply, which is factually accurate, only has 1 point...

      --

      The AACS key is NOT 0xF606EEFD628B1CA427BEA93A9CA9773F
    20. Re:Ok, I'll bite. by jimicus · · Score: 1

      I'm talking about a secondary school and student computers - think "ages 11-18".

      I looked into an NT migration, and found that in theory it was possible but there was one minor glitch. My boss at the time demanded that a single specific program run or he wouldn't sanction such a migration.

      This specific program was an application launcher designed to make things easier by allowing an admin to set up and group a handful of single-click icons to launch applications - desktop icons and the start menu being deemed "too difficult". And it didn't work on NT at all.

    21. Re:Ok, I'll bite. by Anonymous Coward · · Score: 0

      Win32s exposed enough functionality that you could install IE 4 on Windows 3.11. Talk about ugly! ;)

  17. Very Nice Link... by bigdavesmith · · Score: 5, Funny

    The Borg Cube bearing the Microsoft logo, destroying Earth, with flames reaching up from off-frame image just screams professionalism. I will take anything this site says very seriously.

    1. Re:Very Nice Link... by westlake · · Score: 1
      The Borg Cube bearing the Microsoft logo, destroying Earth, with flames reaching up from off-frame image just screams professionalism. I will take anything this site says very seriously.

      The Billy-Borg and stained glass Windows icons of Slashdot invite the same response. The same is to be expected from BadVista.org, of course.

    2. Re:Very Nice Link... by poot_rootbeer · · Score: 1

      The Borg Cube bearing the Microsoft logo, destroying Earth, with flames reaching up from off-frame image just screams professionalism. I will take anything this site says very seriously.

      Yes, avoid all sites with graphics that suggest some sort of relationship between Microsoft and the Borg.

  18. So? by Robber+Baron · · Score: 2, Interesting

    What Microsoft faces in 2007 is not going to be the lack of OEMs selling Vista for them, but the unraveling of its monopoly position and its ability to mislead the world again with promises of new, next generation technology just around the corner. We know better than that now. So? Tell us something we don't know.
    Microsoft makes operating systems and office/productivity apps, and that's about it; nothing magical or "next generation" about that.
    Don't expect "next generation" and you won't be disappointed.
    BTW Linux is still staring at its own navel...
    --

    You're using her as bait, Master!

    1. Re:So? by Salsaman · · Score: 1
      Linux is still staring at its own navel...

      What do you mean by that, exactly ?

    2. Re:So? by Teun · · Score: 1

      BTW Linux is still staring at its own navel...

      Well, it is prettier than most!
      :)

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    3. Re:So? by Anonymous Coward · · Score: 0

      He's saying that Linux has been sitting on it's ass doing nothing but stare at itself, rather than thinking outside the box. The fact that nothing innovative or revolutionary has come out of Linux either. I'll reference Solaris: it has *new* technologies, most notably dtrace, zfs, and zones (and BrandZ by extension). What exactly has Linux offered the world that is NEW?

      I respect the excellent work of the Linux developers, but said fact remains.

    4. Re:So? by Salsaman · · Score: 1

      I have no idea, I am not a kernel developer. But the purpose of a kernel is simply to manage devices, filesystems and processes. Linux does all of those extremely well. But there have been a lot of innovations in the desktop and application space.

  19. Damn, that was crap by perrin · · Score: 3, Informative

    Please give me back the 10 minutes reading that article took me. I am by no means a historian of the computing era, but I lived through those years reading computer magazines and programming the things, so I have no problem seeing bullshit presented as history when I encounter it. That guy is such a flaming Apple apologist, he can't even get his head around the fact that despite all its short-comings, win32 had pre-emptive multithreading and protected memory for all of eight years (1993 vs 2001) before Apple got out a consumer OS with the same. Apple nearly died waiting for its vapourware before it bought NeXT. And Microsoft got into that game late, too, and I mean really late. It was implemented in Unix and other systems in the 1970s. He forgot to mention Windows 3.1, which was one of the most important Windows releases ever, because it proved to the world that Windows could succeed. WordPerfect thought it couldn't, and died. Most sat on the fence for Windows 3.0, because while it was pretty, it was horribly unstable and lacking in essential OS features.

    1. Re:Damn, that was crap by Anonymous Coward · · Score: 1, Insightful

      Are you kidding? Windows 3.x was essentially a DOS extender and was probably the most unstable, widely sold operating system of all time. Even Microsofties heaped scorn upon it afterwards. It was based on cooperative MT, not preemptive MT. Critical GUI resources were limited to 64K on a systemwide basis. Many users were force to reboot several times a day because of an "Unrecoverable Application Error". Interprocess communication and component integration relied on a succession of convoluted "technologies" (really just hacks): DDE, OLE1, and OLE2 Compound Documents. Microsoft had a huge edge over its rivals in application software because it knew the quirks of its own OS better than anyone else, and BEFORE anyone else, so they could workaround problems and take advantage of more robust and performant paths in the API.

      Windows 95 was a major improvement, but was still a far cry from a robust operating system. (The Mac was no better in terms of stability, although it had a much more useable UI). Yes, there was Windows NT, but that was marketed to corporations and wasn't backwardly compatible with DOS applications. Stable, widely adopted consumer OS's didn't appear until after 2000, when Microsoft released Windows XP and Apple came out with OS X.

    2. Re:Damn, that was crap by hedrick · · Score: 2, Informative
      >despite all its short-comings, win32 had pre-emptive multithreading and protected memory for all of eight years (1993 vs 2001)
      >before Apple got out a consumer OS with the same.

      Win32 is an API, not an OS. Protected memory is an attribute of the OS, not the API. If we're talking about significant consumer implementations, the first serious implementation of win32 would be Windows 95. (Earlier ones were NT 3.51 and Win32s in Windows 3.1.) That's 1995.

      The Mac equivalent to the win32 API would be Carbon. I agree that the first real protected mode implementation was 2001, with OS X, though I'm not convinced that anything before 10.2 was commercially significant. That's in 2002.

      But that's still a long gap. While some had a different experience, during that gap I remember that every time my Mac staff wanted to show me something, their systems hung. I told them to come see me again when they had a real OS. Of course now they do, and I prefer it to XP/Vista.

    3. Re:Damn, that was crap by bonefry · · Score: 1

      Windows NT started from the OS/2 3.0 codebase which was developed jointly by Microsoft and IBM ... so Microsoft cannot receive full credits for it.

      Windows 9x had pre-emtive multitasking for 32 bit applications, and cooperative multitasking for 16 bit applications, at least theoretically. And everyone here knows that Windows 9x provided real quality, especially Windows Millennium ;)

      Mac OS Classic sucked, yes, but it was much better than Windows 9x which was replaced by Windows XP in late 2001.

    4. Re:Damn, that was crap by Bert64 · · Score: 1

      Those same critical GUI resources are still limited systemwide, only now they're limited to 16Mb.
      They don't fix the problems, they just push them further out of the way.
      Out of interest tho, how difficult would it be to write a program specifically to allocate as many of these resources as possible (to cause a dos), and is it possible with something like a word macro?

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    5. Re:Damn, that was crap by siride · · Score: 1

      Actually, Windows 3.1 had preemptive multitasking, but all Windows apps ran inside a single preemptively multitasked process. DOS apps ran in their own preemptively multitasked processes. This whole system was extended in Windows 95 so that each Win32 application had its own preemptively multitasked process and only Win16 apps would still share a single process. Windows 3.1 also had virtual memory, but again, since there was only one process, it was effectively used as a way to extend the amount of memory available rather than creating separate protected virtual address spaces for each application. And it was badly implemented, a problem that continued through the 9x series.

    6. Re:Damn, that was crap by julesh · · Score: 1

      Win32 is an API, not an OS.

      Win32 is also an informal name used for the set of operating system that support the Win32 API, i.e. the entire NT family of Windows operating systems, plus Windows 95, 98 and ME.

    7. Re:Damn, that was crap by Foolhardy · · Score: 1

      Windows NT 3.1 was released in 1993. It had fully protected memory, strict user/kernel separation (i.e. only the kernel can touch hardware devices), and fully preemptive multitasking (even for threads running in kernel mode). Windows NT 3.1 marked the first implementation of Win32. NT wasn't marketed as a consumer OS until version 5.1 (XP) in late 2001, but NT 3.1 was offered as a general purpose OS with plenty of overlap with DOS/Windows 3.1. It could run many Win16 and DOS programs, as long as they used Windows, DOS and BIOS interfaces to access hardware (as opposed to 9x which usually didn't care).

    8. Re:Damn, that was crap by drsmithy · · Score: 2, Informative

      Windows NT started from the OS/2 3.0 codebase which was developed jointly by Microsoft and IBM ... so Microsoft cannot receive full credits for it.

      No, Windows NT *was* the OS/2 3.0 (ne: NT) codebase. Microsoft alone worked on OS/2 3.0, although by that time most of the work in OS/2 2.x was IBM's.

      What went on to become OS/2 3.0 was a further development of OS/2 2.x by IBM, *not* the codebase that went on to become Windows NT. Even a cursory examination of their architectures should make it obvious that Windows NT and OS/2 have next to nothing in common.

      IBM were still paying Microsoft royalties for their code in OS/2 *4.0*.

      Windows 9x had pre-emtive multitasking for 32 bit applications, and cooperative multitasking for 16 bit applications, at least theoretically. And everyone here knows that Windows 9x provided real quality, especially Windows Millennium ;)

      Relatively, it was competitive.

      Mac OS Classic sucked, yes, but it was much better than Windows 9x which was replaced by Windows XP in late 2001.

      Er, no. MacOS of the day couldn't hold a candle to Windows 9x in anything except UI (and even that is debatable). Windows NT utterly eclipsed it.

    9. Re:Damn, that was crap by poot_rootbeer · · Score: 1

      And Microsoft got into that game late, too, and I mean really late. It was implemented in Unix and other systems in the 1970s.

      But those had been designed to be multi-user systems. It took a decade or two for single-user computer use patterns to reach a point where cooperative multitasking wasn't good enough anymore. For that matter, it took a while for desktop computers to become powerful enough that multiple jobs could run simultaneously without decimating responsiveness.

  20. An inconvenient truth by MCSEBear · · Score: 1

    One thing I'm tired of in the Windows Vista/Mac OSX comparisons is the claim that indexed search was a Vista feature first. I'm afraid Mac OS has featured Indexed search since Mac OS 8.5 was released in 1998 with Sherlock. Sherlock was based on the Apple Advanced Technology Group's V-Twin search engine. Sherlock did a full index of text in documents on all hard drives and allowed users to search on document contents before Longhorn was even a code name.

    Now, Microsoft did promise to have a database file system with search way back in the Cairo dark ages. Cairo never shipped. They promised it again for Windows Longhorn. But they never shipped WinFS did they? The search feature in the final version of Windows Vista is from a little company that Microsoft bought so they would have some kind of desktop search to compete with Google's. Well, actually MSN bought them.

    Vista did not have full indexed search before MacOS since this has been a shipping feature for Apple since 1998!

    Mac OS 8.5 with Sherlock

    1. Re:An inconvenient truth by SEMW · · Score: 1

      One thing I'm tired of in the Windows Vista/Mac OSX comparisons is the claim that indexed search was a Vista feature first. I'm afraid Mac OS has featured Indexed search since Mac OS 8.5 was released in 1998 with Sherlock. Sherlock was based on the Apple Advanced Technology Group's V-Twin search engine. Sherlock did a full index of text in documents on all hard drives and allowed users to search on document contents before Longhorn was even a code name. If you want to define fast searching as anything that uses an index, then Windows XP would qualify as well, since it used indexing. As did all versions of Windows since 95. As did, as you say, Mac OS. And yes, previous versions of Windows could search inside files just as Mac OS could. You boast that "Sherlock did a full index of text in documents on all hard drives and allowed users to search on document contents before Longhorn was even a code name" -- which is perfectly true, but utterly misleading, since Windows 95 could so the same before Sherlock was even a code name.

      The equivalent of the fast searching capability that Vista uses isn't Sherlock, but Spotlight. As to the question of which of them was the first with this, the correct answer is -- neither of them, since Copernic Desktop Search predated both...
      --
      What's purple and commutes? An Abelian grape.
    2. Re:An inconvenient truth by MCSEBear · · Score: 1

      Windows 95 could search the contents of documents, but not against an index. Each time you did a search it would slooooowly search the contents of documents one at a time. Indexed searching first appeared from Microsoft as part of Internet Information Server, not as part of the OS.

    3. Re:An inconvenient truth by SEMW · · Score: 1

      I apologise; you're right, 95 didn't have indexing -- but 2000 and XP both did (though I think it was disabled by default). My main point would be unaffected even if 2000 & XP didn't have it (that indexing (which Mac Os 8.5, 2000, & XP all used) is not by itself the same as the fast searching technology used in Spotlight and Vista).

      --
      What's purple and commutes? An Abelian grape.
    4. Re:An inconvenient truth by x2A · · Score: 1

      Didn't the index service originally come with Office rather than as default with Windows? I remember always turning it off, as I rarely ever need to search, and it slowed my comp down constantly as it was indexing.

      --
      The revolution will not be televised... but it will have a page on Wikipedia
    5. Re:An inconvenient truth by MCSEBear · · Score: 1

      Internet Information Server's Index Server was indeed the basis of indexed search in both Windows 2000 and Windows XP. You are right when you say that it was disabled by default. Search in Windows Vista was supposed to be based on WinFS but is in fact based on code from a company MSN bought.

      Since Windows 2000's disabled version of indexed search shipped a couple of years after Mac OS 8.5, I'll stand by my assertion that indexed search of file contents and metadata was a feature that was a shipping part of Mac OS long before it was demoed as a vaporware feature of the WinFS in Longhorn.

      I don't really see a whole lot of difference between the search features of Sherlock and the search features of Spotlight or Windows Search. What features are in Windows Vista's Windows Search that were not already shipped by Apple as part of MacOS 8.5 in 1998?

      After some brainstorming I've come up with 'search as you type', but that has been a shipping feature of iTunes since it's first version in 2001. It's also been a shipping feature in Apple's spotlight for a couple of years now... hardly a Microsoft first.

      Windows Search lets you search the contents of e-mail as does Spotlight, but Apple's Cyberdog also did full indexed searches on email back in 1996. A full two years before Sherlock shipped. (FYI - Cyberdog also used the Apple Advanced Technology Group's V-Twin indexing and search engine just as Sherlock did later.)

      Here's an image of Sherlock getting ready to preform a custom search. Notice that it is set to search file metadata such as the contents of the 'comments' field of the files properties. So we have a full indexed search engine shipping as part of the OS and enabled. It searched files and file metadata. What am I missing?

  21. where are the feetures .. by rs232 · · Score: 2, Interesting

    Remember they were included in Cairo in some form in 1995. Vaporware as usually described, is announcing something that don't exist in the hope of warding off the opposition from entering the market and also with the full knowlege that such feetures are not implementable in a realistic timeframe. Else why haven't we seen the pre-announced features even now in late 2006.

    "The top level will .. [be] the Cairo desktop itself .. Cairo's Object File System (OFS) makes the whole hard disk a single huge docfile that exposes its internal objects to the user"

    "In Daytona's successor, Cairo, OLE structured storage will be able to attach to, and extend, the file system",

    "Microsoft's future object-oriented file system for Windows NT (see the sidebar "A Peek at OFS"). Ultimately, we could be looking at a distributed file system based on this technology .. Almost all this technology is expected to converge in Cairo"

    "Object File System Lets you create a pseudodirectory that unifies local, network, and Internet files"

    http://www.dynamicobjects.com/d2r/archives/002430. html

    was Re:Better Windows history here...

    --
    davecb5620@gmail.com
    1. Re:where are the feetures .. by cnettel · · Score: 1

      OLE structure storage was present as alternate NTFS streams in NT 5 Beta 2 (and maybe also Windows 2000 beta 3, not sure anymore). Some Office files could become strange when saved on such partitions, especially when later accessed over the network. It was dropped from the actual release, but this also means that it was present, in a limited way, in Real Code. There's also a lot of support for storing keywords/properties for individual files in NTFS and exposing some of it in Explorer, but "nobody" uses it.

    2. Re:where are the feetures .. by twitter · · Score: 1

      Taking out the non operative words, we have:

      OLE structure storage was present as alternate NTFS streams in NT 5 Beta 2 ... [but did not work and was not released] ... but ... it was ... Real Code.

      Did not work and never saw the light of day is who's idea of software?

      --

      Friends don't help friends install M$ junk.

    3. Re:where are the feetures .. by Anonymous Coward · · Score: 0

      OFS actually existed inside MS and was used daily by those on the Cairo team, but it just never worked out.

      The idea of files within other files was cool and it worked pretty well on local files because it cut out a layer of abstraction. However, accessing the files over the network meant separate operations to open/read/close each individual subfile, which made using the files over a network slower than regular docfiles. On top of that, no other program ever written knew about those files, so you couldn't easily use them over HTTP or FTP, Zip them, copy them to a USB drive, etc. Since it is no good to have files that you can only use on your local hard drive, the only way to make it feasible is to store both the single-file version and the multi-file version, and automatically convert between the two on the fly!

      ReiserFS will have the same problem, BTW. MacOS doesn't have the network slowness problem because it only uses 2 forks on a file, but it definitely has the file transfer problem. To this day you can't transfer Mac files containing resource forks with FTP without first converting to BinHex, MacBinary, StuffIt, or some other proprietary format -- or with OS X transferring both the file and its hidden twin.

      To add insult to injury, OFS was a completely new filesystem. Who would want to trust their files to a new, untested FS when NTFS was already mature and robust?

      Anyway, the indexing engine ended up shipping as a feature with IIS. Other minor features like the security descriptor index, object IDs, link tracking, and mount points were added to NTFS in 2000.

      dom

  22. It's not a Windows History. by twitter · · Score: 1, Troll

    Wikipedia - generally a little more authoritative than a (rather opinionated and flawed) blog entry. Incidentally, I distinctly remember Cairo not being vaporware or a hoax as stated in the article,

    The Roughly Drafted article is not supposed to be a Window's history, it's a Microsoft Marketing history. Versions of software are mentioned and compared to competing and promissed versions. The history presented is accurate as are the product descriptions. What's more important is how M$ prommisses everything their competitors have today, convince the press the promisses are credible, but fail to deliver for decades. To find the same information in Wikipedia, you need to combine the Microsoft specific information from these articles:

    Or you could just have a memory and a brain. It should be clear to any Windows user that M$'s operating systems are bloated, insecure and feature poor. It is equally clear that the reason for their market dominance has everything to do with marketing and nothing to do with technology. The author goes into some of those mechanics and why they won't work in the future.

    The central thesis, that M$ uses vaporware to it's advantage, is clearly true. The similarity between Cairo an Longhorn mostly exist because Microsoft has yet to deliver on the feature promisses they made for Cairo. As the author pointed out, those features were available in competing products of the day and many are still not implemented in the new 10 Gigabyte sized Windoze.

    Specifically, Cairo promised to deliver:
    • an object oriented user interface, featuring direct manipulation of desktop objects like OS/2 already had
    • an object oriented development environment like the one already offered by NeXT
    • distributed computing features like those offered by NeXT
    • an object or database file system that would replace the flat file system with a fully searchable object store
    • a standards based messaging system like Lotus Notes
    • a standards based directory system just like Novell's NDS

    Yes, when I say many, I refer to the lack of standards and use "Embrace, Extend Extinguish" delivers after a decade of fumbling. You can run in circles forever with slippery M$ promisses, or you can get out and enjoy standards based software from innovators. This has been the case for decades.

    --

    Friends don't help friends install M$ junk.

  23. this is COMPLETELY WRONG. by Anonymous Coward · · Score: 0

    Windows NT does *NOT* stand for Nested Task. That's complete misinformation, either made up by the parent or by the friend of the friend of whoever he got it from. NT stands for "New Technology". The fact that the parent post is modded "+5, Informative" reveals something about the experience level of Slashdot moderators... many of them are probably high school and college kids.

    1. Re:this is COMPLETELY WRONG. by DrSkwid · · Score: 1

      > Windows NT does *NOT* stand for Nested Task.

      They have better reading comprehension than you. I didn't say Windows NT stood for anything

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    2. Re:this is COMPLETELY WRONG. by Anonymous Coward · · Score: 0

      > They have better reading comprehension than you. I didn't say Windows NT stood for anything.

      Maybe you should've posted about EFI = Electronic Fuel Injection then. That doesn't have anything to do with the name "Windows NT" either!

  24. Monopolies can do this. That's why they're illegal by dpbsmith · · Score: 1

    IBM was exactly the same way. And big corporations and the trade press hung on IBM's vaporware announcements the same way.

    Once a sole company dominates the marketplace as thoroughly as Microsoft today or IBM a few decades ago, the sensible corporate types and the trade press hardly bother with the competitors.

    Who cares whether Control Data or Burroughs or Amdahl makes better computers than IBM? They can't win. Who cares whether the Mac OS or Linux is better the Windows? They can't win.

    If you believe the future is inevitably Microsoft, it doesn't matter if it bungles its plans or reneges on its promises or manipulatively changes its direction. Because a murky view of Microsoft's future is more important than a clear view of the competitors' present. Because the competitors have no future, or at any rate not one that matters.

    So everyone goes along happily listening to Microsoft's rosy fantasies, and when they don't materialize everyone will shrug and say "But look, it's still a lot better than XP."

  25. Show me a better summary by twitter · · Score: 1

    I am by no means a historian of the computing era, but I lived through those years reading computer magazines and programming the things, so I have no problem seeing bullshit presented as history when I encounter it.

    I lived through it too but I agree with the author's assertion that the trade mags of the time were full of shit and that M$ still is. In the end, it's hard to disagree with the author's well documented thesis: that M$ conned the wintel press into comparing existing software to M$'s future vision. The details are less important than the big picture because it will keep you from being fooled into thinking Vista is competitive.

    This is one of the best summaries of M$ marketing practices I've ever seen. If you have a better feature compare, spanning two decades, I'd like to see it.

    --

    Friends don't help friends install M$ junk.

  26. Re:NT = "N-Ten", working name for the Intel i860 by cpeterso · · Score: 1



    http://en.wikipedia.org/wiki/Intel_i860

    Microsoft initially developed what was to become Windows NT on internally-designed i860-based workstations (codenamed Dazzle), only porting NT to the Intel 386 and other processors later. It is often rumoured that the original meanings of the 'N' and 'T' in Windows NT was for "N-Ten", after the working name for the i860 core.

  27. EVERY enemy of MS's is Slashdot's friend by Anonymous Coward · · Score: 0

    This is nothing new. Just another irrational, ranting, foaming at the mouth Microsoft hater.

    His article is like porn for Slashdot zealots: extremely skimpy on fact, and complete hatred against all things Microsoft. Nothing gets headline status around here quicker than an article reinforcing Slashdot's anti-MS FUD.

    1. Re:EVERY enemy of MS's is Slashdot's friend by DECS · · Score: 2, Interesting

      If something is factually wrong in the article, why don't you point it out?

      Sounds like you are just dismissing anything that doesn't fit your narrow world view.

  28. Re:Monopolies can do this. That's why they're ille by wellingj · · Score: 1

    I don't think the point of Gnu/Linux is to 'win'.
    The point it to provide a free alternative that works better.
    And since it does not behold to the same economic pressures
    that most software does, I don't see microsoft makeing it go
    away as easily.

    But that's my oppinon...you can choose what ever OS you want to.

  29. Re:Monopolies can do this. That's why they're ille by the_humeister · · Score: 1
    Once a sole company dominates the marketplace as thoroughly as Microsoft today or IBM a few decades ago, the sensible corporate types and the trade press hardly bother with the competitors.

    Who cares whether Control Data or Burroughs or Amdahl makes better computers than IBM? They can't win. Who cares whether the Mac OS or Linux is better the Windows? They can't win.


    This shows two things:
    1) Control Data no longer exists, Amdahl isn't doing so well after being absorbed by Fujitsu, and Burroughs merged with Sperry to form Unisys (which, as of 12/2006 is in the red).

    2) Monopolies don't last forever.
  30. Windows preemption is crap by joe_n_bloe · · Score: 1

    Honestly I don't know what Windows does to "preempt," but before NT the scheduler was crap, after NT the scheduler was crap, process control has always been broken, the UI locks up and can't be restarted, anything other than a bare bones install can take minutes to shut down and/or require two or three "shut down" requests and/or manual process kills (which themselves can take minutes and/or cause lockups), and then there are things like the goofy user interfaces for networking and services. Protected memory never meant a thing for Windows stability, or if it did, I'd hate to think what it would have been without it. So, whatever.

    I've never thought that Eran's articles were any loopier than those from other computer pundits. They're long and kind of dull but perfectly within the bounds of reason. It's a columnist's (= opinion writer's) job to be provocative, not balanced. Apparently Eran's mistake is wanting to participate in a fanboy blogsite whose noise level puts Slashdot's to shame. His being banned from Digg is a headscratcher, but the average Digg poster is a lost cause anyway.

    1. Re:Windows preemption is crap by x2A · · Score: 1

      Ever tried killing a zombied process in linux? Or a process that died trying while trying to read from a file over died network mounted FS? 2.6.17 seems to have improved on the latter, but that's pretty recent. And, if the UI hung on a Mac you were in just as much trouble, their processes didn't even have private address spaces, but just one flat unprotected address space.

      Point is, all OSs have had their flaws... you spend more time looking for the flaws on one particular OS, and you're gonna find more than on any other. Which ever OS it is.

      --
      The revolution will not be televised... but it will have a page on Wikipedia
    2. Re:Windows preemption is crap by Stardate · · Score: 1

      Linux, like all POSIX OSes, is designed not to allow a process which is blocked on I/O to be killed except by rebooting the system. However, it doesn't prevent you from using the rest of the system, dropping to a shell, using X, etc. When Windows gets screwed up, it can be very hard to kill certain processes which are not allowed to be killed just by virtue of what they are (CSRSS, winlogon, and certain services which can only be seen as svchost.exe or services.exe but which can take up 99% CPU all the same). These are critical system processes, but they are running in user mode, not kernel mode, so they should not take the system down, but they effectively do. Hopefully this will improve in Vista.

      --
      "... I declare our city to be a free and independent state to be named Tri-Insula!" --Fernando Wood, Mayor of NYC 1861
    3. Re:Windows preemption is crap by x2A · · Score: 1

      "However, it doesn't prevent you from using the rest of the system"

      That's incredibly naive, of cause it can. You want to reconnect the dropped network connection, but can't because it's "already mounted", and can't be unmounted because a process has an open blocking file handle within it? Or you wish to unmount the partition/network share that the process itself is running on? What if you need to make changes to the process binary or another file that it has open and locked, and can't until you close it? Okay, it might not stop you from doing something /else/, but that doesn't help if the thing you're using the system for is deadlocked until you reboot it.

      "is designed not to allow a process which is blocked on I/O to be killed except by rebooting"

      So it's not even a bug, it deadlocks by design?! And you think this helps your case how exactly?

      And as for certain processes which cannot be killed/easily killed... yeah? What OS doesn't have those? That's like expecting to be able to kill the dcopserver and expect konqueror to keep running. Yes, you can "drop into the shell", but if the program you're in the middle of using was using dcopserver, what help is that?

      "certain services which can only be seen as svchost.exe or services.exe"

      Start -> Settings -> Control Panel -> Administrative Tools -> Services... they're all right there (you can even create a shortcut on the desktop to it if you really need). It's also scriptable using the 'net start' and 'net stop' commands.

      Yes there are processes that you cannot kill under Windows... unlike Linux's kjournald, kswapd, kthread, cifsoplockd, ndis_wq...

      Like I said, it's easy to find flaws in the OS you're looking for them in, because they exist everywhere, in Mac OS, Linux, Mac OS, Windows, AND Mac OS. But it's just plain naive to pretend "your favourite OS(tm)" doesn't have flaws simply because you've never given them any thought time.

      --
      The revolution will not be televised... but it will have a page on Wikipedia
    4. Re:Windows preemption is crap by ratboy666 · · Score: 1

      Interesting examples...

      A "zombie" process is already dead. Of course you can't kill it. The PARENT must be killed.

      As to network i/o waits... This is by design. The NFS server is stateless, and can be rebooted. It is possible to mount these in an interruptable way, but this is not (generally) recommended.

      A process may be in the kernel -- if a device driver fails, it will not be killable. This may be due to software failure, or hardware failure. But this is not one of your mentioned cases. Both of your cases are "by design".

      You are correct. Linux, Solaris, etc. have flaws. But be careful when labeling an effect you are observing a "flaw". It may be an implementation of "proper" semantics (Linux, Solaris, BSD, AIX etc. all suffer from the two "problems" you pointed out -- they are actually proper semantics).

      Ratboy

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    5. Re:Windows preemption is crap by ceswiedler · · Score: 1

      A zombie process is dead already, there's no point in killing it. It only exists to provide a return code to its parent. Processes whose parent has exited are reparented to init, which immediately checks and discards the return code. Therefore, zombie processes always have parents which still exist, and those parents may be interested in the return code from their child. If you were allowed to kill the zombie child process, then what do you propose waitpid() return to the parent when it's called?

  31. Thank you for the info on gaming digg by nietsch · · Score: 1

    I really can't tell if you are right or wrong, but it seems your description of how to get to the frontpage of digg works very well. Nice to know if I ever might need it. Thank You!

    --
    This space is intentionally staring blankly at you
  32. Bull... Once more for those who skipped class by Anonymous Coward · · Score: 4, Insightful

    Being a monopoly is NOT illegal. It is leveraging the monopoly in an anti-competitive manner that is illegal.

    Items 1, 2 and 4 on your list are just good business sense. Monopoly or not.

    But "3. Working with third parties to offer incentives to provide your product solely." is illegal. If you leave off the word "solely" its ok, but when your "incentives" come off like strong-arm bullying, and the "solely" provision is the primary objective, that is anti-competitive. That is also what Microsoft was (repeatedly) found guilty of.

    And from what I've seen and heard of Vista, application of the other three items is questionable.

    1. Re:Bull... Once more for those who skipped class by newt0311 · · Score: 1

      Mod parent up. a lot.

    2. Re:Bull... Once more for those who skipped class by DECS · · Score: 3, Insightful

      Actually exclusive deals are not illegal, and maintaining a monopoly often is.

      Try googling news for "exclusive deal," and tell me how many of those are illegal. There are lots of examples of exclusive business deals.

      However, while monopolies are allowed in specific areas where it is determined that competition would create more problems that it would solve, the existance of legal monopolies (for cable, power utilitites, water) generally overlap into areas often supplied by the government (municipal transportation, power, water), not competitive industries.

      In competitive industires, monopolies are generally illegal. When Lowes Theaters bought AMC Theaters, it was forced by the state of California to divest itself of certain theaters so that it wouldn't own the majority of outlets in certain markets. That happened despite the fact that AMC/Lowes didn't even own all the theaters and had significant competition.

      Microsoft's monopoly in operating systems was defined as a monopoly in the court, and found to be abusive in the narrow portion of evidence that was actually considered. Significant efforts were presented to solve that illegal monopoly and abuseive use, but then the current administration swung into power and dismissed any and all action.

      So no, despite the rule of law being uninforced in America, monopolies are not generally "legal" just because an anonymous coward says they are. That's a myth. The US has a long history of breaking up monopolies and companies that exercise undo influence over markets. In other countries, including Europe and Asia, monoploy control is more common and not always illegal. Massive conglomerations are typical in Japan and Germany, but were always frowned upon in the US, back when the rule of law was enforced.

      Illegal monopolies are not legal any more than illegal wars are legal. Just because something is allowed by a kowtowed populace and an uncritical press does not mean that the law does not exist or that it will never be enforced. Just wait until the red states have a moment to consider how much money they have lost! Once that happens, the US is sure to have a revolution of sorts and elect an administration more interested in enforcing the laws than in distractions of jews, flag burning, gay marrage & all the problems caused by minories.

    3. Re:Bull... Once more for those who skipped class by GaryPatterson · · Score: 2, Insightful

      "So no, despite the rule of law being uninforced in America, monopolies are not generally "legal" just because an anonymous coward says they are. That's a myth. The US has a long history of breaking up monopolies and companies that exercise undo influence over markets. In other countries, including Europe and Asia, monoploy control is more common and not always illegal. Massive conglomerations are typical in Japan and Germany, but were always frowned upon in the US, back when the rule of law was enforced."

      Daniel, I'm generally a fan of your site but you're going off-base with this bit.

      The US gov't only breaks up monopolies that start exerting undue influence because at that point a company crosses the line from benign or natural monopoly (eg power station to a region) to a monopoly that's misusing its power to tie products (eg Windows + IE) or force anti-competitive practices (eg Microsoft + forced Windows licencing on new PCs).

      A monopoly in and of itself isn't bad or strange. They *are* generally legal, until they start breaking the law. Governments across the world will allow a monopoly quite happily for as long as the company acts within the law.

      Massive conglomerations aren't frowned upon in the US any more that the rest of the world, and many of the largest have their home in the US (such as GE). They're not at all bad, until they start breaking local laws.

    4. Re:Bull... Once more for those who skipped class by DECS · · Score: 3, Insightful

      I'm glad you like my site.

      However, as in the example I gave, antitrust policy is the way the US works. GE, GM, and General Mills might be big companies, but they are not conglomerates on the scale of German and Japanese companies, where mega umbrella companies enter and control multiple markets. As a sloppy example, Mitsubishi does everything from banking to heavy industry, oil, real estate, steel, cars, ag, beer, logistics, insurance, and it even cans tuna.

      No American groups can do that because of different economic policies on competition. In the US, there are laws preventing companies from dominating industries and distorting competition, let alone owning multiple industries. The US similarly has had far less support for nationalized utilities.

      The US government always investigates mergers and acquisitions to make sure that comeptition won't be distorted as companies converge. Back when Aldus and Adobe became Adobe, the company had to divest itself of Aldus Freehand (because it also had Adobe Illustrator); It sold it off to Macromedia.

      Things have changed. When Adobe bought Macromedia, it stripped the software world of far more competition, but no action was taken. Adobe didn't have to get rid of Macromedia Freehand for Adobe Illustrator this time around, nor did it have to allow Dreamweaver and GoLive to remain in competition, and any of a number of other examples. The difference is a change in politics and economic thought.

      Despite that shift, monopolies are only allowed where competition is unlikely to benefit consumers. Newspapers in a city are often allowed to join in non-competitive joint contracts to fix prices on advertising, keeping ad prices artificially high in order for newspapers to cheat off obsolescence. But that doesn't mean its legal for gas stations to collude on price fixing too.

      Making blanked statements that "monopolies are legal as long as they're not hurting anyone" is similarly misinformed, particularly under the rather arrogant title "Bull... Once more for those who skipped class," so I had to jump on it.

      I'm a sucker for arguing against anonymous cowards I guess.

      Why Microsoft Can't Compete With iTunes

  33. The article needs rewriting, but the point is good by Futurepower(R) · · Score: 1

    The article is poorly organized. Slashdot's story about the article does not quote the most important parts. Slashdot readers have commented on the Slashdot story with numerous irrelevant points.

    The article is a description of what is reasonably, in my opinion, called fraud. Quote: "After a half decade of being presented as a legitimate competitor to NeXT's object oriented development tools and various other products, Cairo was revealed as a complete hoax."

    The author is trying to stop the "Fraud as a Business Plan" practiced by Microsoft. (There is also a need to stop incompatible file formats as a business plan. Open Office is excellent, and free, and uses an ISO standard file format.)

  34. Who is this clown? by windowpain · · Score: 1

    Daniel Eran's site is a terrible mishmosh that doesn't look good in Firefox or IE. In Firefox there were giant-sized gray letters superimposed over the text. On IE at the highest level of text magnification the type was still on the smallish size. His narrative seems to be a disjointed, stream-of-consciousness diatribe that meanders and folds back upon itself.

    For example, on this page:

    http://roughlydrafted.com/RD/Q4.06/4E2A8848-5738-4 5B1-A659-AD7473899D7D.html

    There's a weird picture of a Windows logo with blue lines and flames. Click on it and you get a page entitled "1990-1995: Why the World Went Windows."

    On that page there's a link entitled "1990-1995: The Race to Deliver the Next New Platform IBM and Microsoft partner on OS/2."

    Okaaaay. Well a lot was happening in those years, after all. But if you click on that link you bring up a page entitled "1990-1995: Hitting the Wall." Say what?

    I'm embarrassed for the poor schmuck. One of the downsides of the Web is that it allows people to soil themselves in public.

    --
    Insert witty sig here.
  35. Re:Show me a better summary by Anonymous Coward · · Score: 1, Informative
    twitter, please read this carefully. Following this advice will make Slashdot a better place for everyone, including yourself.



    • As a representative of the Linux community, participate in mailing list and newsgroup discussions in a professional manner. Refrain from name-calling and use of vulgar language. Consider yourself a member of a virtual corporation with Mr. Torvalds as your Chief Executive Officer. Your words will either enhance or degrade the image the reader has of the Linux community.
    • Avoid hyperbole and unsubstantiated claims at all costs. It's unprofessional and will result in unproductive discussions.
    • A thoughtful, well-reasoned response to a posting will not only provide insight for your readers, but will also increase their respect for your knowledge and abilities.
    • Always remember that if you insult or are disrespectful to someone, their negative experience may be shared with many others. If you do offend someone, please try to make amends.
    • Focus on what Linux has to offer. There is no need to bash the competition. Linux is a good, solid product that stands on its own.
    • Respect the use of other operating systems. While Linux is a wonderful platform, it does not meet everyone's needs.
    • Refer to another product by its proper name. There's nothing to be gained by attempting to ridicule a company or its products by using "creative spelling". If we expect respect for Linux, we must respect other products.
    • Give credit where credit is due. Linux is just the kernel. Without the efforts of people involved with the GNU project , MIT, Berkeley and others too numerous to mention, the Linux kernel would not be very useful to most people.
    • Don't insist that Linux is the only answer for a particular application. Just as the Linux community cherishes the freedom that Linux provides them, Linux only solutions would deprive others of their freedom.
    • There will be cases where Linux is not the answer. Be the first to recognize this and offer another solution.



    From http://www.ibiblio.org/pub/linux/docs/HOWTO/Advoca cy

  36. Novell = NeXT? by oatworm · · Score: 1

    After reading this guy's article and a few of the side articles that it links to, I realize that the point he's trying to make is:

    1. Apple made the Next Big Thing (Macintosh).
    2. Apple sat on its lead and did nothing (OS 7, 8, 9; attempted to sue Microsoft, Copland, etc.)
    3. Apple was saved by acquiring vision from a failing competitor (NeXT)
    4. Profit!

    Meanwhile...

    1. Microsoft made the Next Big Thing (a Macintosh-like interface that worked on computers people could actually afford - Windows 95)
    2. Microsoft is sitting on its lead and is doing nothing (Windows Me, Vista, odd security glitches, etc.)
    3. ???

    He claims that Microsoft is sitting square at #2, trying to live off vaporware and bloat. Since Microsoft isn't going to get away on its own, now what? But, what company is out there that Microsoft could purchase that could give Microsoft everything it needs (an OS that runs on commodity hardware) without all of the baggage, is failing enough where Microsoft could get away with buying it, and which supports other parts of Microsoft's stack (Mono, OpenExchange)?

    That's right - Novell.

    After reading the articles and looking at the market, I sincerely think that Microsoft is getting ready to groom Novell and the market for a NeXT-like sweep of the market, replacing NT with Linux, replacing VB with Mono, replacing Exchange with OpenExchange, and maybe even propping WINE up to kill some time, sort of like Mac and its Classic environment.

    Am I insane?

    1. Re:Novell = NeXT? by Cassini2 · · Score: 1

      There is no way that Microsoft could co-opt Linux to replace it's brain-damaged O/S development efforts. Linux and Windows have simply developed too far in incompatible directions. Further, the day that Microsoft even mentioned "maybe we should switch to Linux", everyone would immediately stop purchasing from Microsoft. Linux is free.

      A more likely scenario is Microsoft going the way of the old IBM mainframes. Initially, IBM really dominated all computing of any consequence. The IBM vision was not a low-cost vision. As such, the old DEC PDP and VAX minicomputers were developed and sold at much lower prices. Eventually, the IBM PC came along. The PC was cheaper than the mini-computer, and had a new totally different and incompatible operating system. The PC eventually became the dominant form of computer.

      Today, we see Linux in a huge number of embedded applications (like the PS3 or the TiVO). These are less expensive computers than a PC. Eventually, we may see that these embedded machines are present in greater numbers than the PCs running Windows. When this happens, this will be the end of Windows as the dominant operating system. The PC marketplace will have fundamentally changed at that point. This shift may not be that far away. Google is already running Linux, and the ranks of embedded devices are continually increasing. Linux devices may already outnumber Windows PCs. We just haven't noticed it yet, because we are so PC focused.

    2. Re:Novell = NeXT? by NSIM · · Score: 1
      Am I insane?

      Based on that flight of fancy, I think a case could be made.

  37. I've posted this before, I'll post it again by jrobinson5 · · Score: 0

    Mr. AC, I see you post this same reply to twitter every time he posts.

    Exhibit 1

    Exhibit 2

    Exhibit 3

    Exhibit 4

    Exhibit 5

    Exhibit 6

    Exhibit 7

    In fact, the list goes on, you seem to have posted this same reply verbatim to every single one of twitter's posts! Just look at the list of posts made by twitter and notice every single one of them, starting on a certain date, has the same reply by you, verbatim. I dunno what you have against twitter, and while I certainly don't endorse his claims, it seems stupid for you to harass him like this.

    (if you weren't an AC I would guess karma whoring, as most of these replies tend to get +5)

  38. Infamy only partly deserved by petrus4 · · Score: 1

    This isn't the first time I've read one of this guy's articles. He makes his biases clear right up front, and they aren't subtle...so you might want to be cautious of that. He's a very heavy advocate of Apple, which always leaves a bad taste in my mouth, but for all that he writes well and occasionally makes valid points, when he isn't busy telling us about how Steve Jobs is supposedly the Messiah. There are also some surrealist charicatures of Steve Ballmer which I'm sure Ballmer wouldn't find flattering.

    He also has a good grasp of history...he knows the 80s well enough that I can only assume he was alive at the time. For that alone, his articles are worth the price of admission, since even if you don't agree with his final premises, you'll get enough out of the 80s side trips that it won't much matter.

    1. Re:Infamy only partly deserved by tehcyder · · Score: 1
      He also has a good grasp of history...he knows the 80s well enough that I can only assume he was alive at the time.
      You make it sound like he's a survivor of the Crimean War or something.
      --
      To have a right to do a thing is not at all the same as to be right in doing it
    2. Re:Infamy only partly deserved by petrus4 · · Score: 1

      20 years (roughly the length of time since the 80s) is more than a quarter of most people's lfetimes. It isn't the Stone Age, but it's not insignificant, either. In order to have been an adult at the time, he would have to be at least 45 years of age today; presumably older.

  39. Nice Try by AJWM · · Score: 1

    That's what I figured it stood for. As in "nice try, but it's not quite there yet". Or maybe it just stood for "nearly there".

    --
    -- Alastair
  40. And Cutler Says by Anonymous Coward · · Score: 0
    1. Re:And Cutler Says by Anonymous Coward · · Score: 0
      "VMS + 1 = WNT" makes no more sense than "IBM - 1 = HAL"

      No less, either.
  41. Why does this man deserve mention here? by Dputiger · · Score: 1

    I realize that not all Slashdotted stories are created equal, but for crying out loud, Daniel Eran isn't just a lousy writer--he fills every single one of his "articles" with factually incorrect statements, absurd leaps of logic, and demonstrates a consistent failure to apply proper rules of analysis to his own conclusions. Ever since I saw him blithely carve the concept up "market share" into a pie graph whereupon it was possible for Microsoft to hold 48% of the PC hardware market due to OS shipments, I've been waiting for people to stop giving him traffic. It's not that he writes articles that challenge other people's pre-conceived notions--it's that he writes articles that demonstrate a profound personal stupidity and a total lack of understanding concerning how data is properly presented and filtered in order to demonstrate a correlative (much less conclusive) relationship. (research methods, in other words).

  42. Another inconvenient truth by Daltorak · · Score: 1

    Now hang on a minute. It's one thing to talk positively about what Mac OS 8.5 was accomplishing back in 1998, but if you're going to talk about Windows, at least get your facts straight!

    First of all, nothing Apple has shipped up to now even comes close to what WinFS was trying to solve. It's not a search engine... it's a relational database store for arbitrary user data that presents content to the operating system as a series of "entities". Comparing WinFS to a content search indexer is missing the point. See WinFS. Frankly, it's a good thing that they waited, because they have piles of other things to fix with Windows before they introduce something this drastic.

    Microsoft shippied the first version of their content indexing service in mid-1996, though it was really the Content Indexer component that was part of the Object File System aspect of Cairo. That was announced in 1991. It didn't ship as a standard component that would do system-wide indexing until 2000, but it has been there all this time. Microsoft did buy a company in July 2004 called Lookout to get their Outlook indexing capabilities, which was then rolled into MSN Desktop Search.

    The problem, of course, was that the Indexing Service UI sucked horribly. Most Windows 2000 users haven't even seen it because they don't know it's there! Then again, most long-time Mac users will tell you that Sherlock has always sucked on OS X, and suffered from its own problems of not being sure if it was a program to search your local drive, or to search the Internet.

    In short: Lame duck vs. lame duck.

    Oh, and, MSN Desktop Search (the first non-crap search indexer from Microsoft) shipped before OS X 10.4 with Spotlight (the first non-crap search indexer from Apple), but that's not something a Mac user would say, right? :-) The content indexer included with Vista and MSN Desktop Search are almost identical code-wise, and is merely an evolution of what's been around in Windows for many years. See Windows indexing service. Now we just gotta wait a little bit longer and see what Apple does to top Microsoft's offering in Vista.

    Should be interesting...

    1. Re:Another inconvenient truth by MCSEBear · · Score: 1

      LOL... Microsoft shipped disabled indexed search as part of their operating system in 2000. Apple shipped enabled indexed search as part of their operating system in 1998. Those are the facts to get straight.

      Vaporware bullshit that never shipped just doesn't count. Not Cairo or WinFS or Copeland or Pink or whatever. Vista did not beat MacOS to the market with indexed search. Microsoft will offer an enabled version of indexed search suitable for normal users next year in Windows Vista. Apple's been shipping it since 1998 as Sherlock and for the last couple of years as Spotlight.

  43. News at 11 by Tom · · Score: 1

    trying their best to discourage competition in the marketplace. Microsoft? Seriously? Now that would be a first, wouldn't it?
    --
    Assorted stuff I do sometimes: Lemuria.org
  44. Credibility is Questionable by PixieDust · · Score: 2, Interesting
    From just these two statements:

    Windows 3.0 gets polished and becomes Windows 95? hardly, as these two Operating Systems are vastly different, with their only real similarity being they both run on top of DOS.

    Windows XP gets polished and becomes Windows Vista? Again, hardly, as again they are VERY different. XP And Vista are much closer than 3.1/95, but they're still worlds apart. Feature sets are very different, capabilities are very different, overall user experience is VASTLY different, and checking things out under the hood a lot has changed, and it's kind of interesting to see just how much. Yes a lot of features were unfortunately dropped, but there is still a lot here to chew on.

    I saw earlier a comment saying the blogger is a spammer. Somehow, that wouldn't surprise me. It's an MS flame article though. Can we mod front page articles -1 flamebait? ;-)

    1. Re:Credibility is Questionable by vaporland · · Score: 1

      Don't understand why everyone hates this guy so much (Eran). He's amusing and occasionally literate, certainly more insightful than Ron Pergaro or Cringley. I am fairly certain that some of the spamming attributed to him is being perpetrated by others who just don't like him very much.

      --
      Ask Me About... The 80's!
  45. Re:how about google by SillyNickName4me · · Score: 1

    When I go buy a coffee in many of the places around, I get some bit of coffee creamer with it, regardless of if I ask for it. If I explicitly tell them waiter to not include it, it usually (but not always) won't be there.

    That said, none of those places insist on putting the creamer in the coffee for you and stirring it (usually they will do so when asked however)

    The problem with Microsoft is that they keep insisting on doing something similar to putting in the milk and stirring.

    Not a big problem for me personally, I just don't use their products. It is a big and costly problem when looking at it with a bit more of a bird's eye view however.

  46. Finish this saying: "Fool me once....." by Anonymous Coward · · Score: 0

    Well, can you finish it? So how deep are you bowing your head in shame? I think so deep it is all the way up your ass because you keep buying MS products.

    In dutch we have a saying about a donkey, they don't hurt themselves on the same stone twice. Have you got the brains of a donkey?

    Ah no, offcourse not. This is IT were common, business, sense does not apply. If a regular supplier wrongs you, you never deal with them again, in IT, you keep coming back for more. Yes sir, thank your sir, can I have another SIR!

    This is not just a slam against you or MS. It is the same with companies that complain about Dell yet buy Dell. It is about all those big IT projects that keep going to the same company no matter how many times it has gone over budget and over time to deliver an inferior product. Every country has their own version of it BUT it is always the same story. Countless blunders and the next project gets assigned to them again.

    What is perhaps even most amazing is that nobody even bothers to come up with excuses. Past performance just doesn't seem to exist in IT. It is almost as if when you work in IT your memory is surgically removed. This has been done with rats (short term memory anyway) and the rats will then do the same stupid thing time and again because without their short term memory they just can't learn from past mistakes.

    If you stub your toe on the same table time and time again, don't blame the table. Blame yourselve. Perhaps IT should go into one of those programs for abused wives who keep going back to their husbands. That or a cattle prod. "Wow that MS sales rep I talked too AAARGH!!!!"

    1. Re:Finish this saying: "Fool me once....." by SmurfButcher+Bob · · Score: 1

      Ordinarily, I'd tend to agree.

      However, the "ass" comment is not appropriate - you haven't considered, AT ALL, the vertical market that many enterprises are involved in. Mine is not the only head up an ass, per-se. You are using the exact same tactic that MS has done; promising vapor that does not, and will not, ever exist.

      In our industry, there are exactly four vendors today. In the past, there has been as many as six.
      There are about 53 possible customers for these vendors in the US. If we also add Canada, the count increases to 56.

      It's a cool $1.3 to get up and running, and the bulk (probably $800k) is software and labor. This assumes a vendor will have at least seven customers, so that their costs are reasonably distributed across their customer base. Less than that, historically, they do not stay in business, since the software costs become too high if it is redistributed across the existing customer base (which the vendor cannot do, anyway, for at least the term of the contracts that are involved).

      The competing software platforms are complex. You'll not buy them at "CDW", and you will not find them on freshmeat. Ever.

      Please, feel free to apply your argument to this obvious general case that you have flatly overlooked. 50-odd customers, cut amongst 4 vendors. The average vendor will need at least 5 clued developers, who's skills are FAR beyond "coding", and one dedicated support tech per customer. They'll also need a tech manager to coordinate the tech knowlege, since an issue impacting one tech may likewise impact another. Oh, you'll need a sales pig, also. They aren't cheap... especially when there's only 50 possible customers, each of which typically contract for 3 to 5 years at a time. Sales pigs can count on lots of sales to pay their mortgage, obviously.

      I'd suggest that the challenge isn't that I keep buying MS products - the challenge is that VENDORS keep writing for them. Like I said... find me a vendor with a linux back-end, TODAY, that does what I need, and I'll get it. Or, OSX. I don't care what it is. You'll fail.

      The application is pretty simple... you'll need a GIS engine. You'll need the ability for authenticated users to interactively edit a map in a browser (full layer and arbitrary polygon drawing support, not some "google maps" bullshit), with full version and reversion control. You'll need this back in 1999, by the way. You'll also need a method for a call-taker to take relevent data from a caller, and enter it. You'll need the ability to bounce that information off of a map, to tag features that the aformentioned "authenticated users" had created. You'll need to then compile a list of which "authenticated users" had a feature that was involved, and send them a copy of the data that was taken from the caller. You will NOT notify a user if they had no involvement. Again, you'll need this back in 1999. Technically, you'll need this in 1986. But, who's counting.

      The data must be pushed to a given user via either fax, modem, email, xml, pager, or voice (human) dispatch, and the delivery must be guaranteed (in a very legal sense) with full supervision and auditing. For a given user, the method(s) used (may be plural) and people/systems contacted will vary by time of day, day of week, holidays, context of data, or a small pile of other factors, including error conditions on the far-end. Once received, a user will process this data, and eventually "feed" a disposition about it, back to us. You'll need the ability to receive these dispositions via IVR, web form, XML, telnet, or modem, and it'll need a measure of authentication (especially fun where IVR is concerned). These dispositions will need to be made available to the original caller via www on-demand, and also "pushed" to them via fax, email, or automated voice. Note that the "caller" is the general public. Again, you'll need this back in 1999. Or, 1987. Both dates should be trivial for you, obviously.

      Depending on geography and time of year, you'll need to process about 3 to

      --

      help me i've cloned myself and can't remember which one I am