Over the past few days this site has had a ridiculous number of hits outside its ordinary audience. This seems to be due to two particular referrals at the same time, both referencing my post on Leopard showing networked PC’s with blue screens of death:
Unfortunately, the StumbleUpon community seems to be somewhere around the Digg level of maturity when it comes to reviews:
We have a Warren-esque remark about how the site content is “OLD” (let alone the fact that it was written in June, and was a spur-of-the-moment type thing based on a preview copy of Leopard). Strike one.
We also have a superior-than-thou comment about how the poster has never seen a BSOD on XP, and is now going to play some “award-winning games” on his machine. I can hear the Comic Book Guy’s snickering now.
I’ve had kernel panics on OS X. I’ve had random “bus error” messages appear while using Disk Utility on the Mac – hence the title of this freaking weblog. (I’ve never had that horrible of an error message occur personally on any other operating system.) And I’ve had blue screens on 2000, XP, 2003 Server, and Microsoft’s latest pride and joy, Vista – and in Vista, they’ve been incredibly perplexing to troubleshoot.
Operating systems of all kinds can and will die unexpectedly. I don’t play the game of platform superiority anymore. I find Windows does better for certain tasks, such as a seamless 1.8TB storage pool for all my media and personal files. (I’ll have a post on Windows Home Server and its ass-kickery soon enough.)
I find the Mac does better for other tasks, such as managing my 60GB+ music library with iTunes. I don’t have the time or patience to determine why a Core 2 Duo E6750 can’t organize folders locally in half the time my MacBook can over the LAN. After years of tweaking Windows settings, I’m content to let the Mac manage things and find out solutions to idiotic problems when it’s convenient, not when I want to listen to Mims.
In any event, users probably wouldn’t notice XP bluescreening anyways, as its default settings are to dump memory contents to disk and reboot immediately. I’ve fixed many a system with dodgy motherboards that needed this option disabled, to confirm that the chipset drivers were acting up. A split second is not enough time to ascertain the driver file name or the STOP message.
So, commenters of StumbleUpon, I salute you for your wonderful sense of timing and self-satisfied gaming. Any other takers?