August 11, 2004 - 2:38 pm
Apparently, last weeks stint in Microsoft Certification Training (aka Billsoft Brainwashing) didn’t stick with me. I learned enough to feel confident breaking new stuff at work, but not enough to change my opinion on Big Brother Bill. (Have I mentioned how much I hate trying to make all the cool web design stuff work in IE? I’m not bitter, but… well, okay, I’m bitter.)
Windows XP has been out long enough now that I feel fairly comfortable with it. It’s really not a “bad” operating system. If you must use Windows, this is a pretty good version.
Unfortunately, XP has also been out long enough that MS is ready to screw it all up. Thus Service Pack 2 (SP2) is all geared up. Very soon, your friendly neighborhood Windows Automatic Update will quietly deliver all sorts of “new features” courtesy of XPSP2.
Now, to be totally honest, most of the features of XPSP2 sound alright. But there are just a few troublesome “helpful features” (aka “You’re too stupid to be trusted, so we’ll quietly add features that take away your ability configure your own computer.”).
SP2 was originally written to force Automatic Update. That is to say, you would no longer have the option to pick and choose what Windows Updates you installed. Instead, when MS posted an update, your machine would go get it and install it without asking your permission. Sadly (snicker snicker, nudge nudge), some countries have passed laws preventing this behavior. If Microsoft (or anyone else) wants to install code on you’re machine, they MUST give you the option to “opt-out”. Thus, this feature had to be removed (whew). Instead, Microsoft.com‘s home page is splashed with trendy looking banners imploring you to “Get ready by turning on Automatic Update today!”.
SP2 introduces an OS firewall. For my layman readers, that means that Windows itself will block certain types of connections to or from your computer. That’s fairly harmless if you’re just an EISU (E-mail, Internet, Solitaire User; someone who only uses their computer for simple tasks). But if you use your PC to, say, share music files or run a web or game server, this firewall could be a real headache. And, it does nothing to prevent things like spyware, that use the internet (port 80) to do their dirty work.
Also, since the pop-up blocker industry has become such a huge threat to Microsoft’s revenue, (please read that as dripping with sarcasm), MS has decided to add this “helpful feature” to IE. Gee thanks. You know those widely accepted, standardized functions like javascript’s window.open()? Well, you can forget those, cuz they’re (insert scary “ooh ooh” sound) DANGEROUS. Never mind the fact that most high end web applications, such as on-line banking and cool sites that help you find a doctor who takes your insurance, use pop-up windows. Those web applications will break when XP starts blocking those pop-up windows.
SP2 is bad enough that IBM has issued a stern warning to employees, “Don’t install SP2 on your work PC!” IBM, as you can imagine, has all sorts of really cool web applications for internal use. And if folks who use those applications install SP2, those cool web applications will break, bringing IBM’s internal workings to a crawl. All this time IBM has been one of MS’s biggest fans. Now they’re peeing in each other’s soup. It’s kinda fun to watch.
What could be worse than Microsoft introducing code that tears up the internal network of its biggest ally? How about introducing code that breaks its OWN software. Yep. Microsoft announced that SP2 will break Microsoft CRM, a customer support system that my own company has been wrestling with for months. We’ve just about got CRM working with our network and ready to roll out and now, SP2 will break it anyway. Nice.
So, what’s the bottom line? What should I do when Automatic Update chimes and tells me that SP2 is here and all I have to do is click one little button to receive this manna from Redmond? Personally, I’m going to wait. I can install the service pack whenever I want. I prefer to watch everyone else wail and gnash their teeth first. Then, when someone comes along and posts all their hard earned work-arounds, I’ll “patch-up” and take advantage of someone else’s sweat and tears to fix my SP2.
That’s my story and I’m stickin’ to it.