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*
The stuffed mascot in the background looks an awful lot like someone else we know ;)
#!/bin/bash
You are not the customer.
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,
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.
"You compile it today."
"No way--*you* compile it!"
"No way! Hey--let's get Mikey, he'll compile *anything*!"
"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?
I thought it was forged deep within Mt. Doom...
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."
"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.
"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" :)
"...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.
...the War Room is run by Todd Wanke...
Oh dear. Poor Todd.
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.
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
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!
So in a couple of years we'll learn that:
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"?
That "goto" in line 3 prevents lines 4 and 5 from working:
4) ???
5) Profit!
(Not that Micro$oft needs anymore of that.)
That mascot is probably reserved for voodoo rituals :-) Geek or not, it's still MS... :-)
The ENIAC Demo Competition
-fren
"Where are we going, and why am I in this handbasket?"
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.
all brought down routinely by 5 line scripts :(
Boy, its a good thing that no frame buffers are in the Linux kernel.
http://saveie6.com/
I guess it's true: What Intel giveth, Microsoft taketh away...