> your typical large enterprise foces IE down their throats, courtesy of 20+ years of rape by the legions of IT guys who, through the cognitive dissonance inducing Microsoft certification/training/tools process now think that everything Microsoft is magic

I can't speak for every company, but in my experience there's much more to it than that.

A large part of the problem is that many of the tools leveraged by Enterprises (which are purchased from vendors) to develop web applications are extremely brittle and sensitive to the user's browser. When you talk about pushing a new version of IE, every web tool in the company (easily dozens) needs to be examined to determine the impact and cost related to making sure it works with the new version. This often means pushing new versions of these vendor packages as well, and the costs associated with that planning (think of the management effort required) and implementation.

In many Enterprises, this is infrastructure overhead and is largely avoided (it's a huge headache/cost) until absolutely necessary. "Absolutely necessary" means when the vendor (MSoft) stops supporting that browser version. Which doesn't happen until it is well past obsolete.

Of course, management gets many of these concepts from those Microsoft Certified developers, but that's not the whole story.