Nearly 80 years ago, the term "planned obsolescence" was coined by Bernard London, a New York City real estate professional and amateur economist. The idea, which London thought was a darn good one, was to design products with a limited lifespan so consumers regularly had to get new ones, thus keeping the economy going.
This is why you don't see many 1983 Ford Escorts tooling around. While cheap old cars rust out or fall apart, software should keep chugging. "Unlike hearts, lungs, knees, eyes or kidneys, software just doesn't wear out or get weak," says reader Fred Linton. But old software ends up just as obsolete as your junk Ford. That's because vendors choose to make it that way.
Even though code doesn't stop working unless corrupted, software goes out of date in a variety of ways. The biggest death blow strikes when vendors stop support. No more features but, more critically, no more security updates.
Another problem is when new environments won't run old products. Even if a new version of Windows looks and acts largely the same, many older applications and hardware no longer operate.
Redmond magazine heard from some 30 readers -- all IT pros -- about their frustrations with unsupported software and how they deal with them.
Read the full post
