Windows Vista: New and 60% Improved


Up to 60% of the code in the new consumer version of Microsoft new Vista operating system is set to be rewritten as the Company “scrambles” to fix internal problems a Microsoft insider has confirmed to SHN.

In an effort to meet a dealine of the 2007 CES show in Las Vegas Microsoft has pulled programmers from the highly succesful Xbox team to help resolve many problems associated with entertainment and media centre functionality inside the OS. The team are also working closely with engineers from the Intel Viiv team. and it is now expected that the next version of Viiv could be delayed to line up with the launch of the consumer version of Vista at the 2007 CES Show in Las Vegas. [Emphasis mine]

Granted, this is almost certainly silly taken literally — Windows is million of lines of code, so rewriting is not like a redrafting a book chapter — but it still wouldn’t surprise me to find out that there is a substantial restart going on somewhere under the hood.


  1. There is no way this can be even in the slightest bit accurate. I mean, think about it- it took, what, 6 years to get this far, and they are supposed to be rewriting 60% of it in 4 months? That’s just completely and obviously bogus. I’m not a huge Scoble fan, but he is outraged by this claim, and rightly so.

  2. This is balderdash. There is no way you can rewrite and test even 15% of the code of a complex system this close to release in a year.
    There are two possibilities:
    Several years ago, the Vista (Longhorn) effort was scrapped and restarted, though I seriously doubt 60% of the Windows code was involved with that. (And it was never labeled a rewrite.)
    There is some credible speculation that the 60% number concerns only the MCE (Media Center Edition) subsystem. This subsystem is heavily connected to DirectX which, in turn, is at the core of Vista. This would very much explain the delay–they simply can’t afford to get this one wrong.
    Insiders claim nobody has been moved from the XBox team. However, if this has to do with DirectX, it means the XBox team is involved. It would indicate a fundamental incompatibility between the two implementations of DirectX. If this is the case, kudos to the manager who had the balls to make the call for a delay (far too many companies would have said “screw it, let the end developers figure it out.”)
    (One thing about Microsoft that has always garnered respect from me is the willingness to cut non-working features when this close to shipping. That they chose to instead slip the release tells me the problem is in a core subsystem.)