4 ms·
You could still apply Group Policy’s to later versions of IE as well. So that wasn’t the reason. It was more to do with corporate apps being tied to specific ve
by laumars 5y ago
You could still apply Group Policy’s to later versions of IE as well. So that wasn’t the reason. It was more to do with corporate apps being tied to specific versions of IE due to later versions of IE having breaking changes in the way it rendered content vs earlier versions of IE.
Those of us who remember web development in the 90s and early 00s will vouch for how the pain wasn’t just supporting different rendering engines, but even different versions of the same rendering engine.
- dejongh 5y agoAgree. Early web development was a compability nightmare. Now that one platfrom rules the world it is less of a problem. It seems that making a standard failed, and we solved the problem by adopting the same platform.
- trulyme 5y agoAs someone who went through browser wars and lived under IE tyranny, I hate this point of view (which is pretty common, unfortunately). What happened is that standards finally got their act together, and FF was eating IE's lunch anyway. Chrome just sped up its demise. But, monoculture is never a good thing. Especially as the leading company is actually an advertising agency. Do you think we can trust them not to abuse their position?