There are bugs that bug the user and bugs that lead to catastrophe. Below lie two examples of critically-buggy applications, which I recently decided are worth listing.

1. Windows 95 – Blue Screen of Death

I still remember, as a most classical example, the days of Windows 95. The operating system failed to cope with unhandled, misunderstood packets that ultimately gave the blue screen and required a reboot in most cases. Sooner or later people got hold of so-called ‘nuking’ software — one among virtually dozens of GUI-based free downloads. That little tool gave its owner the ability to unleash upon others the infamous ‘blue screen of death’.

IP address of the target computer was all one needed. It was easy to determine one’s IP address even when dynamically allocated by a dial-up ISP. Instant messengers (ICQ was new and hot at the time) simplified the process tremendously and tools that interacted with the IM existed as well. This gave your friends and foes the ability to ‘take you down’ whenever they desired.

Sooner or later, anti-nuke software was becoming mandatory. Yet another application to run in the background if you want to survive without rebooting and losing some invaluable work. Not good.

During the holiday, yet another critical flaw with Windows XP and Windows Server 2003 was found. Lessons have not been learned even 10 years later. The promise and efforts to make Windows more modular seem unfruitful.

2. Timely Example: WordPress 2.0 Bugs

I previously said that the release of WordPress would be premature. I said so as soon as rumours emerged. Matt Mullenweg spoke about an undetermined release that precedes Christmas. Boxing Day was the point when things took a gentle dive.

I now write about 40 messages a day in the WordPress support forums, making a voluntary contribution throughout the holidays, as promised. The pace of bug reports is worrisome. That aside, the WordPress Web site was not prepared for the demand either. There was a site migration issue on the very same date as the release and coding bugs emerged all too soon in the forums where they continue to resurface.

WordPress 2.0 was intended to be named after a Jazz musician, as always. ‘Stan Getz‘ was among the top contenders. I believe that WordPress should not be called Getz because it might give a favoured artist of mine a bad name. WordPress 2.0 is more like Milli Vanilli (sarcasm and an overstatement).

Earlier today a version database downgrader for WordPress was released. A few people regret the upgrade, but many are very happy with the new features. Whether the frustration supercedes the benefits is an important question. The answer is yet difficult to deliver and the situation hard to judge.

This entry was posted on Thursday, December 29th, 2005 at 12:43 pm and is filed under O/S, Opinion, Programming. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.