2 ms·
I'm really not sure you can have this both ways. Either you use a modern, up to date browser and code to standards (and thus reduce your coding workload and mai
by chris_wot 14y ago
I'm really not sure you can have this both ways. Either you use a modern, up to date browser and code to standards (and thus reduce your coding workload and maintenance), or you can code to an old, out of date browser.
The fact is, the main reason that he wants people to upgrade to IE10 is to reduce the support and maintenance burdens of supporting old browsers with weird javascript and rendering bugs. The heading is, after all "Old technology is wasting everyone’s time and money". The solution I put to everyone is to stop supporting IE8 and install Firefox. You can even deploy it via Active Directory and update it via Group Policy, AFAIK.
So the simple solution is to switch to something like Firefox. Or you could continue to support IE8. It's really not ideal to do both, which you'll need to do if you have Windows 7 or above given you will almost certainly have IE9 or above on these installs.
- gnaffle 14y agoThe main problem is all the internal webapps that were written to support IE6, still works with IE8, and are very costly to rewrite, upgrade or replace. So in many cases they have to _add_ Firefox, they can't simply replace IE. That means even more user training (what, they've installed a second internet with a fox on it? Which should I use??), so the more tempting option is to just sit it out and wait, because they know that they will have to upgrade to Win7 or Win8 next year anyway if they still want security fixes.