The elephant in the room here, and one that is completely ignored by this article (AFAICT) is corporate web apps.
A constantly moving target, which auto-updates silently, is anathema to the average half-baked corporate web app. They're half-baked for a reason: they have a limited budget, a limited customer set whom they mostly trust, and need to be maintained in parallel with lots of other apps by understaffed development teams working in companies whose main business is not software.
Perhaps MS needs two browsers, or some other solution. But I can't see them moving to a fast-iterating model without a radical shift in where they make their money - i.e. their business model.
It also helps them that you still can't manage Firefox settings remotely for your desktop estate, and you can't change policy across all your users instantly. Both of these give IE massive traction.
Comments
The elephant in the room here, and one that is completely ignored by this article (AFAICT) is corporate web apps.
A constantly moving target, which auto-updates silently, is anathema to the average half-baked corporate web app. They're half-baked for a reason: they have a limited budget, a limited customer set whom they mostly trust, and need to be maintained in parallel with lots of other apps by understaffed development teams working in companies whose main business is not software.
Perhaps MS needs two browsers, or some other solution. But I can't see them moving to a fast-iterating model without a radical shift in where they make their money - i.e. their business model.
It also helps them that you still can't manage Firefox settings remotely for your desktop estate, and you can't change policy across all your users instantly. Both of these give IE massive traction.
I think that's the "compatible mode" (i.e. an old IE6 engine) ?
it doesn't work all that great on my corp intranet.