Thursday, 20 August 2009

Preparing to update...

In the old days you'd buy a piece of software, install it, and if there were any bugs you just had to live with them until the new version was released. If you were really lucky the software producer might write a patch for some of the more crippling bugs that would be distributed via free floppy disks on PC magazines...

Because of this, I feet that software producers (and hardware manufacturers, come to think of it) put a lot more effort into making sure their software worked the first time.

Then along came the internet! Suddenly we didn't need to worry about finding the patch on a floppy disk. The programs we used could tell us when they needed updating and even update themselves automatically. For a while this was all good and well, software developers knew that most people (if they had the internet) were only connected by, at most, 56kbs so updates were kept to the essentials. Security patches, big crash fixes and virus definitions.
Eventually; along came ADSL and always-on internet. Now every piece of software wanted in on the action. Some lazy software developers could launch half baked products and push a multitude of patches onto the user at a later date, dressed up as additional features. "Oh I've now got version 2.2 of BLA" we'd think. "And look, they've fixed the bugs that were in 2.1 and added some new features, sure the new features have bugs but they'll be fixed in 2.3!".
And so the cycle continued...

Arguably, these days, there are more reasons to update software. The way we connect our computers together and share information between them means that malicious code can be spread far faster than in the pre-internet era, software developers need to be able to react to new vulnerability in their code that would have been a none issue 15+ years ago.

Now we've got to the stage where hardly a week goes by where my printer decides it needs to update itself... "Why?" I ask myself, "why do you need to update when my documents were printing perfectly fine before?". I wouldn't mind so much if they just quietly updated in the background but that seems to be too much for some applications, forcing Windows Vista to request administrator access (a feature I love by the way) and thus, interrupting my work-flow.

"Product X has downloaded updates, click here to apply them" Is another favourite... Why do they bother asking, half the time the program won't work until the update is applied anyhow!

The regularity with which the windows JVM would update was a running joke among my peers for a while, requiring an update almost every time the machine was started. Or so it felt!

To their credit Microsoft have come a long way with regards updates, no longer can we use old joke window of "Microsoft Windows has detected your mouse has moved and must restart to continue". Unfortunately they've also gone back a few steps as well. Now it would seem that Windows Vista becomes impatient with the user and eventually a small dialogue box appears with "Windows will restart in 2 mins to apply patches". Now, I hate this dialogue box for two reasons. Firstly, there's no option to postpone indefinitely only for a maximum of four hours. Secondly, the box will not show if you're using a full screen application such as a game. Several times I have been disconnected from the middle of an epic battle only to have to sit through the painful ordeal of watching windows update slowly while I know my guild-mates are being slaughtered by some dragon...

Ok, rant over...

No comments: