Slashdot Mirror


Inside The Development of Windows NT

mrpuffypants writes "Winsupersite has a 3 part series this month about the history and development of Windows NT all the way up through Windows Server 2003. The author goes fairly in-depth describing how Windows is developed, managed, and how all 50 million+ lines are compiled daily. Part One covers the history of NT from its early days at Microsoft and Part Two discusses how the deployment of the forthcoming server version of Windows is coordinated daily." *shiver*

29 of 681 comments (clear)

  1. hmmm... by garcia · · Score: 5, Funny

    The stuffed mascot in the background looks an awful lot like someone else we know ;)

    1. Re:hmmm... by Anonymous Coward · · Score: 5, Funny

      don't you find it sad that you know that?

      Plus, I think it was pointed out b/c it was the "war-room" and there was a penguin in it.

  2. NT compile script by Limburgher · · Score: 5, Funny
    First line:

    #!/bin/bash

    --

    You are not the customer.

    1. Re:NT compile script by pyrros · · Score: 5, Funny
      Nah, my money is on:
      @echo off
    2. Re:NT compile script by csguy314 · · Score: 4, Funny

      First line:

      #!/bin/bash


      Line two:
      #By compiling this program you agree to the following terms:

      --
      This is left as an exercise for the reader.
  3. WinNT development cycle. by grub · · Score: 5, Funny


    0) CVS checkout the latest net stuff from freebsd.org
    1) Look at code and scratch head until "A-ha!"; enlightenment.
    2) Merge code into Windows source
    3) go to 0

    --
    Trolling is a art,
    1. Re:WinNT development cycle. by ImpTech · · Score: 5, Funny

      > 3) go to 0

      Dijkstra is rolling over in his grave...

    2. Re:WinNT development cycle. by jeriqo · · Score: 5, Funny

      > 0) CVS checkout the latest net stuff from freebsd.org
      > 1) Look at code and scratch head until "A-ha!"; enlightenment.
      > 2) Merge code into Windows source
      > 3) go to 0

      Damn! They use gotos in the development of windows?!
      I know understand why it keeps crashing..

      --
      Alexis 'jeriqo' BRET
  4. There we have it by Anonymous Coward · · Score: 5, Funny

    We thought, 'How hard could it be to build an OS?' and scheduled 18 months to build NT. But we had forgotten about some of the important stuff--user mode, networking, and so on."

    Either this means that the NT team were actually fairly clueless...or incredibly cocky. Either way, that seems like a pretty stupid thing to say.

  5. I can see the round table discussion now. . . by bplipschitz · · Score: 4, Funny

    "You compile it today."

    "No way--*you* compile it!"

    "No way! Hey--let's get Mikey, he'll compile *anything*!"

  6. Security? by elliotj · · Score: 5, Funny

    "By late 1989, the NT group began growing. They added a formal networking team and expanded the security team beyond a single individual who, incidentally, had also been previously burdened by file system and localization development."

    You mean they've got more than one guy working on security for Windows? Oh come on, who's gonna believe that?

  7. Compiled? by patvan · · Score: 5, Funny

    I thought it was forged deep within Mt. Doom...

  8. History of Windows by Toasty16 · · Score: 4, Funny
    Bill Gates: "We need an OS that doesn't suck."

    Engineers: "No problem, we'll release betas every year and you can sell them to the public for the price of a finished product."

    Bill Gates: "Good idea. What do you think Steve?"

    Steve Ballmer: "Developers, developers, developers, developers, developers, developers, developers, developers, developers, developers, developers, developers...*wheeze* *hack* *cough*...."

    Bill Gates: "It's ideas like those that will make you CEO in 10 years."

  9. Punted to longhorn by dracken · · Score: 3, Funny




    "On the day I attended, one feature group had four of its bugs punted to Longhorn because they had failed to shown up for War Room. When someone argued that they should be given another day, Wanke simply said, "F#$% 'em. If it was that important, they would have been here. It's in Longhorn. Next bug."


    Did one feature group have its *feature* postponed to longhorn or the *bug-fixes* postponed to longhorn ? hmmmmmm interesting.

  10. best quote from the article by babycakes · · Score: 5, Funny

    "For Windows Server 2003, the War Room is run by Todd Wanke, who we eventually found to be an amazingly likeable guy. However, in the hour-long War Room sessions, Wanke rules with an iron fist" :)

  11. Incremental build? by BenjyD · · Score: 5, Funny

    "...compiling and linking it into the executable and other components that make up a Windows CD is a 12 to 13 hour process that is done every day of the week

    So they rebuild Windows from scratch every day? Somebody send them a copy of make, please.

  12. Did someone say cocky? by Anonymous Coward · · Score: 4, Funny

    ...the War Room is run by Todd Wanke...

    Oh dear. Poor Todd.

  13. argument clinic by Mr_Silver · · Score: 4, Funny
    If there are one or more bugs in IIS, for example, a representative of the IIS team needs to be present to not only explain the merits of the bug, but whether customers are affected, how the fix might affect other parts of the system, and how soon it will be fixed.

    To be honest, I don't see why they just don't hold these bug fixing meetings around the IIS guys desk :o)

    --
    Avantslash - View Slashdot cleanly on your mobile phone.
  14. Interesting... by tshak · · Score: 3, Funny

    There are 5000 developers on the Windows team generating over 50 million lines of code for Windows Server 2003.

    I think it's safe to say that they're most defniitely _NOT_ using VSS!

    --

    There is no longer anything that can be done with computers that is nontrivial and clearly legal. -- Paul Phillips
  15. Re:Finally... by StressedEd · · Score: 3, Funny

    Off topic but....

    Give a man a fish, he owes you one fish.

    Teach a man to fish, you give up your monopoly on fisheries.


    My favorite...

    Build a man a fire and he will be warm for the night. Set a man on fire and he will be warm for the rest of his life.

    --
    Be nice to people on the way up. You will meet them again on your way down!
  16. NT source by ptaff · · Score: 5, Funny
    Oh, so now we learn that NT is not from "New Technology".

    So in a couple of years we'll learn that:
    • ME: Miserable Everytime
    • CE: Cramped Environment
    • XP: Xor Performance
    • Office: Other File Formats Imply Collaboration: Encrypt!

  17. Secret .NET language leaked by jsse · · Score: 4, Funny

    When someone argued that they should be given another day, Wanke simply said, "F#$% 'em. If it was that important, they would have been here. It's in Longhorn. Next bug."

    C#, J#, S#....now we have F#....shall we pronounce it "Fuck Sharp"?

  18. Where's the profit? by YetAnotherName · · Score: 5, Funny

    That "goto" in line 3 prevents lines 4 and 5 from working:
    4) ???
    5) Profit!

    (Not that Micro$oft needs anymore of that.)

  19. don't be happy by newsdee · · Score: 5, Funny

    That mascot is probably reserved for voodoo rituals :-) Geek or not, it's still MS... :-)

  20. Re:it's tux, troll. by frenetic3 · · Score: 4, Funny
    Waddle does not have a red eye. [iluvcollectibles.com] At least not on the TY site and he was discontinued in 98. You must have been paid to make that silly remark, that or very stupid.
    Where is my "+1, Huge Nerd" mod option when I need it... :P

    -fren
    --
    "Where are we going, and why am I in this handbasket?"
  21. Sounds like typical Micro-FUD to me, bud by ausoleil · · Score: 3, Funny

    Microsoft's record of "innovation" has sunk to a new low -- now it looks like they are going to embrace-extend-exterminate Tux. These bozos can't even invent their own mascot...but then again, a furry, squishy bug (the animal most reminiscent of Windows, IMHO) isn't the most inspiring marketing tool.

    Bet they claim they had a penguin for a mascot all along and it was those hippies, foreigners and un-American freaks that stole their idea and made Tux the mascot for that mean ole' Linux.

    How typical.

  22. 50+ million lines of code! by vena · · Score: 4, Funny

    all brought down routinely by 5 line scripts :(

  23. Re:The NT Kernel Is Good by Billly+Gates · · Score: 3, Funny
    "The NT kernel was good. Then Microsoft moved the GUI into the kernel",

    Boy, its a good thing that no frame buffers are in the Linux kernel.

  24. 12 hours to compile? by lilbudda · · Score: 3, Funny

    I guess it's true: What Intel giveth, Microsoft taketh away...