The InformationWeek -- Blogs
Welcome Guest. | Log In| Register | Membership Benefits

Microsoft

Topics:   Microsoft

  • Email this page E-mail this page
  • Print this page Print this page
  • Bookmark and Share
  • icon

Why Did Vista Stink? Developers, Developers …


Posted by Dave Methvin, Mar 28, 2008 10:01 AM

Microsoft wields incredible power in the computer industry. Still, when it comes to the image of its flagship operating systems, it is greatly at the mercy of third-party software developers. When users sit down to use Windows, the code written by Microsoft sometimes doesn't matter as much as the bugs left behind in poorly written applications and drivers. If a crash happens, the average user is more likely to blame "crummy Windows" than to figure out it's a bug with a device driver.


We rarely get to hear Microsoft's side of the story on this; it doesn't want to publicly berate partners about software quality. Occasionally, though, some unvarnished truth gets through. For example, the folks at Ars Technica have been digging around in the Microsoft e-mails released as part of the "Vista Capable" lawsuit. (CRN has an in-depth story.) Those e-mails had some revealing information about the causes of Vista woes.

According to the Microsoft e-mails, Nvidia's drivers alone caused 28.8% of the crashes seen in Vista during the report period. (The report says only that it covers 2007, but it likely does not cover the entire year.) Microsoft drivers come in second at 17.9%, ATI is third with 9.3%, and Intel takes fourth place with 8.8%. Webroot Software, makers of an anti-spyware application, was next with 2.9%. All the other drivers, from hundreds of companies listed on the report, plus "Unknown", make up the other 32.3% of the crashes.

Cumulatively, this data shows that the Nvidia-ATI-Intel "Axis of Driver Evil" caused almost half of the crashes in Vista! What could Microsoft have done to prevent this problem? A longer beta period probably would not have worked. Vendors weren't going to get serious about making their stuff work with Vista until they were sure that Microsoft was serious about shipping Vista. (If this sounds like a game of chicken to you, then you understand the situation perfectly.) Reports from Nvidia users seem to indicate that their drivers are much better now, but the damage already has been done to Vista's reputation.

Vista's challenge to developers was in the multitude of new security and interface changes that happened "under the hood." Display drivers in particular got a totally new software interface called Windows Display Driver Model, or WDDM. Given the data, it seems likely that a lot of crashes were in drivers that used the new WDDM model. That should not be a surprise to Microsoft; it was a new software technology and nobody had experience with it.

If Microsoft wanted to improve Vista's quality, the best thing they could possibly have done would be to provide more support for driver developers. In particular, they should have carpet-bombed the major display hardware makers with assistance, treated them to "driver ed" classes, and even paired Microsoft experts with the hardware developers to make sure the drivers would be excellent. Or, as Steve Ballmer would say: "Developers, developers, developers, developers."

« And I Recommend Caviar For Dinner | Main | UIQ Platform Updated, Receives Love From SlingMedia »



Sign Up Now
For InformationWeek News Alerts




This is a public forum. United Business Media and its affiliates are not responsible for and do not control what is posted herein. United Business Media makes no warranties or guarantees concerning any advice dispensed by its staff members or readers.

Community standards in this comment area do not permit hate language, excessive profanity, or other patently offensive language. Please be aware that all information posted to this comment area becomes the property of United Business Media LLC and may be edited and republished in print or electronic format as outlined in United Business Media's Terms of Service.

Important Note: This comment area is NOT intended for commercial messages or solicitations of business.




 
 

  1. Massive Parallelism Has a Name ... Extreme Scale Computing
  2. Intel Turbo Boost Technology Monitor: A Windows Gadget to Understand Dynamic Frequencies
  3. Two-Stage Input Parallel Pipeline: Part 2


Join The InformationWeek Group On LinkedIn


  1. Latest Windows Mobile 7 Rumors
  2. Android 2.1 With Multitouch Headed To Motorola Droid
  3. Google's Universal Translator
  4. Rating The Mobile Superbowl Ads


  1. Microsoft Fixes 26 Vulnerabilities In Windows, Office
  2. Intel Ships Itanium Server Processor
  3. Commerce Department Proposes One-Stop Climate Service
  4. Microsoft Denies Windows 7 Battery Bug
  5. Google Buzz Challenges Facebook, Twitter
  6. Android, iPhone Gain In Smartphone Market

 

  Ars Technica
Boing Boing
Channel 9 Forums
CRN Blogs
Dr.Dobb's Portal: Blogs
Engadget
Gizmodo
GrokLaw
  Lifehacker
Schneier on Security
Slashdot
TechCrunch
Techdirt
Techmeme
Valleywag

  DECEMBER 2008
NOVEMBER 2008
OCTOBER 2008
SEPTEMBER 2008
AUGUST 2008
JULY 2008
JUNE 2008
MAY 2008
  APRIL 2008
MARCH 2008
FEBRUARY 2008
JANUARY 2008
DECEMBER 2007
NOVEMBER 2007
OCTOBER 2007
SEPTEMBER 2007