I’m pretty much a beanpole, so I don’t have room to complain, but nobody likes to pop a button off their pants the day they turn a year older. I did that today; kind of demoralizing. Getting older is not my favorite thing, but at least we humans have an opportunity to up our worth each year.

The software we use can’t share that hope. A ridiculous comparison, but I couldn’t help make it after the timing of two events: Only mere minutes after the demoralizing button pop I found myself reading yet another Federal Government RFP including yet another requirement for Windows 98 compatibility. Me, I can shed a pound or two. Windows 98 couldn’t be more obsolete. Buried next to it is Netscape Navigator.

Here’s the skinny on Windows 98:

The most recent edition of Windows 98 was released in mid-1999, so it’s coming up on being nine years old. To put that in perspective, Windows 98 is older than the birth of SCORM and Flash-based video.

Stats released in January of this year tout Windows 98 as holding a whopping .4 percent of the browser market. Even Linux claims 4.4 percent! We don’t have to cater to that bugger! Windows 98 was officially dropped from Microsoft support in summer of 2006, and finally, Windows 98 can’t run either the latest Microsoft browser or the media player. All that means it can be challenging to create cutting-edge web-based products when they MUST function on the Windows 98 dinosaur.

Sure, we can chalk up this archaic requirement to an RFP template being reused for the last 9 years. But let’s not forget that RFPs beget contracts. And contracts beget lawyers. Let’s do a favor to the developers and in turn to our audiences.

Dear RFP authors, please update the specs!