Wow, I have to say I’m glad today is the start of a new year, because after the events of yesterday I wasn’t sure if I could handle another odd day of a particularly odd year.
The crazed over-hyping of a (particularly fascinating) bug in the Zune 30 was honestly a great way to simply sum up 2008. What started off as “are you experiencing what I’m experiencing” on random blogs and forums turned into a bloody full-scale battle, with the tipping point of insanity being the cries of a class-action lawsuit, which I liken to the hardware version of Godwin’s law: when a device has a noticeable flaw, it’s only a matter of time before someone declares that a class-action lawsuit is in order. *
If you were enjoying New Year’s eve with family and friends or busy going about your normal life, you probably didn’t catch the news (unless you have a Zune 30 and it bricked on you). Basically put: many of Microsoft’s Zune 30 devices (and contrary to the “news” reports it was only the 30GB version) had a sudden flair of death in which they had a system-reboot and displayed a progress bar that stuck at 100%. It turned out to be an issue with the internal calendar, and I suspect the specific code was written poorly and didn’t know how to handle a day-count of 366. I didn’t personally see it on my newly received Zune 30 (thanks Mom!) because I had read about the problem prior to firing up my Zune and chose to just wait it out. Although all of yesterday I sat here at my desk with my Zune perched in the corner of my eye begging me to fondle with it, but I was avast in ignored such pleas.
So everybody suddenly panics, many began to open their Zunes up to try and immediately fix the problem (with a hardware solution), which perplexed me since only a software issue could be this precise on a global scale. But their quick actions mostly resulted in the bug repeating itself once the Zune was rebooted. And since older firmware wasn’t affected, it was more proof of the software being at fault.
We now have a perfect example of the pros and cons of updatable firmware. Even with a one-day, once every 4 years flaw, the Zune still beats the mainstream alternative.
And all this happens 2 weeks after a critical 0-day flaw in IE was discovered, which had even IE8 in the crosshairs of the entire industry with random people recommending that we all switch browsers*, even though Microsoft released a patch days after the bulletin was updated to include IE8.
It’s strange, as no one has even bothered pointing out the major flaws that still exist in XP, but I guess doing that might require them to recommend upgrading to Vista, which as we all know must still be as slow and “useless” as it was on it’s release date. (Personally I’m recommending that you hold off until Windows 7—which, no doubt, will be released this summer—unless you really need a more secure system, in which case go ahead with Vista since it is far more secure and you won’t run into driver issues like you might have a year ago. Since Windows 7 builds on Vista—with the snappiness of XP—you won’t need to worry about upgrading from Vista later on.)
So with that, here’s to a new year that I hope will be filled with pleasant announcements from Microsoft (especially on January 15th, for the Mini-MSFT type) and smarter actions taken by bloggers.
FIN
* Regardless, a class-action suit is only applicable in a situation where it’s obvious that the company in question knowingly allowed assumed problem to remain without taking any action or alerting their customers. It seems quite obvious that Microsoft didn’t plan for this and they weren’t purposely bricking devices in order to “cash in” on people ditching their bricked and buying the newer Zunes.
* I would link to another blog post of mine, except I never got around to actually posting it… Perhaps later on I’ll update this to include that future post.