At least not necessarily …

Anyone with a shred of intellectual honesty would notice the following highlighted copyright headers in the widely circulated "embarrassment" that everyone (even those who can't write a lick of C/C++ or ASM) criticized.

zune lie

Unfortunately, too many people blame Microsoft without actually thinking. Freescale may have actually been caught red-handed and with its pants down. Notably, the bug did not affect the Zune models above 30GB. So Freescale knew about the bug, corrected it in a new driver for a new chipset, and then Microsoft may have not been notified.

News agencies were quick to say snarky things like …

"I’ve never heard of a consumer electronic device fail en masse like this,” said Matt Rosoff, an analyst with Directions on Microsoft, a Seattle-based research firm that focuses on the software giant."

Matt Rossoff, you really didn't research anything at your "research firm." VMWare did something massively worse and even similar in 2008!

VMWare's bug was orders of magnitude for significant, and a Zune Bug gets almost as much coverage? Insane.

These things actually happen routinely — in our software, too. It's smart to test for all the edge cases in code (or — even better, mathematically verify it), but missing a bug in code that wasn't actually written by your firm that only occurs on leap years sounds pretty reasonable to me.

The simple problem could have been patched in a routine firmware update any time before the last day of the leapyear — in this case December 31st, 2009.

Are we the only ones who noticed it was a bug in a hardware driver written by Freescale?

The much better question is did Freescale notify Microsoft or cover it up?

Tell an amigo:
  • Sphinn
  • Digg
  • Reddit
  • StumbleUpon
  • Facebook

Related posts:
Microsoft's Anti-Spam Project I said awhile back in my post, Google Violates Computer...
Microsoft the Most Standards-Compliant? Is the world upside down?  By way of Jake's post...