Posted Friday, November 28, 2008 by
PJ Hinton
CNet's Victoria Ho recently wrote an article about
remarks from Gartner and IDC saying that Microsoft's Internet Explorer is too entrenched within large corporations for it to lose market share in that space.
Gartner's rationalizations for continued IE dominance are:
- companies depend on too many applications that tie into Microsoft's HTML rendering engine
- Microsoft provides tools for the centralized administration of IE, something that alternative browsers don't offer
IDC says that it's a self-reinforcing loop. Because IE is the dominant browser in corporate computing environments, application developers will expend the greatest amount of energy making sure their products work on IE.
I don't doubt that there is a mindset that perpetuates this pattern. Last week, I spoke with someone who works in QA for a large web application software development company that still has their computing environment standardized on IE 6, a browser that is broken with respect to standards compliance and way behind the times technologically (example: do you remeber what it was like to browse the web without tabs?)
The irony is that the centralized administration tools cited by the IT analysts empower dinosaur minded administrators to turn their computing environments into technological backwaters, elevating the risk of their systems being compromised by malicious software. As Windows XP support phases out, the updates to IE 6 will cease, making the security issue all the more prevalent.
Eight or so years ago, when Internet Explorer was the pretty much the only game in town with respect to dynamic HTML, one could make the business case that the added functionality in IE justified the lock-in.
Things have changed since then.
The alternative browsers have introduced DOM manipulation through JavaScript, CSS compliance with W3C specifications has improved dramatically, and the adoption of the
XMLHttpRequest object made widespread AJAX development feasible. Several JavaScript libraries have been developed to abstract away browser-specific issues, like incompatible event models, that have hobbled developers from developting for other browsers. Microsoft's ActiveX technology has become so tarnished that
security experts advocate disabling it.
In short, one can develop a modern web application that delivers rich functionality without the Microsoft lock-in and the security holes that they sometimes introduce.
One of the most painful lessons of the recent economic downturn is that the inability to adapt to the times portends a rough, if not fatal, passage for an organization. The plight of the big three auto makers is a prime example of the dire consequences the market metes out to companies that are too entrenched in their ways.
It's also worth noting that when it comes to the startups that are developing the next generation of technologies,
Microsoft's .NET technologies aren't winding up on the development short lists. Microsoft's desperation has escalated to the point where it
launched a program earlier this month to encourage adoption of .NET by startups by dangling free development tools.
The development ecosystem has progressed to the point where web user interface engineers can use third-party libraries to develop their pages using a browser like Firefox and expect it to work on most recent browsers. Some additonal tweaks are sometimes needed to get styling to appear correctly in IE 6, but developers have long agreed that IE 6 is a pain. Firefox has a large number of extensions that make a developer's life a lot easier. To get anything even close on IE, Microsoft requires you to use Visual Studio, which is a bloated approach to the problem.
IE may be the default browser in the enterprise for the near term, but as Microsoft prods customers to migrate away from Windows XP, the reasons that the analysts give for continued lock-in will wane.