Commentary

Dave Methvin
 

Why Did Vista Stink? Developers, Developers …

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.

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.


More Windows Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

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."


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links