Comments on: There is No Looming Windows XP Disaster

By: billybob

billybob — Wed, 17 Jun 2009 14:19:43 +0000

Not because it used IE 6, but because it used ActiveX or generated non-standard HTML via a binary which was not controlled by the company.

ActiveX would be the worst offender for a rewrite, a total dedication to IE 6 standards would be a second place.

By: NickH

NickH — Wed, 17 Jun 2009 13:41:52 +0000

> “Companies that locked themselves into IE 6 applications”.
> “Moving to W7 is going to mean they have to rewrite their internal intranets”

We see customers with problems like this from time to time. Usually, the 99% apps are there, and its one or two specific problems that need addressing. “rewrite” is, in my experience, far too strong a word.

Have you ever had to “rewrite” an application because it used IE6?

By: billybob

billybob — Wed, 17 Jun 2009 12:03:30 +0000

Companies that locked themselves into IE 6 applications are in a very sticky situation now.

Moving to W7 is going to mean they have to rewrite their internal intranets or use the XP mode and have more than twice the support costs.

Maybe business are waiting as long as possible so that they can migrate to Linux rather than W7, it would make sense to wait as long as possible before committing. If they have to rewrite their internal apps then they might as well use the opportunity to write to a standard which does not have vendor lockin so they are not in the same situation 10 years down the line.

Microsoft did a great job of locking companies into Microsoft technology, maybe they were too good at it?