4 ms·

While I am happy too that the new version of IE is coming soon and it supports the latest standards, let us not forget that we all were saying the exact same th

by niyazpk 16y ago

While I am happy too that the new version of IE is coming soon and it supports the latest standards, let us not forget that we all were saying the exact same thing when IE7 and IE8 came out: This new release will help developers very much by supporting the latest standards. The problems is not with supporting a subset of the latest standards. The problem is that the latest standards change over time and IE stays the same for 2-4 years. In the long run, as a web developer I feel that IE7 or IE8 did not help me much in reducing the work I have to do to fix the compatibility issues. Now instead of just IE6, I have to fix issues with IE7 and IE8. (I have had issues where I could fix the problem using some extreme hacks in IE7 while there was no way to fix the issue in IE8. Later I was forced to use the EmulateIE7 meta-tag for the website, which was BTW developed this year. For the curious, the problem was similar to this: http://stackoverflow.com/q/1156985/184 http://stackoverflow.com/q/1156985/184 ) Until unless some version of IE ships with an auto-update mechanism, I will just refrain myself from going gaga over the new CSS/HTML standards support of IE. The most important thing they have to fix is their release cycle (+ auto-update) and they seem to ignore this part for a long time. Now every time a new version of IE comes out, I don't know whether to smile or to cry.

LaGrange 16y ago
They have auto-update. Usually disabled, because people somehow hate windows update, and corporate clients don't really want weird-application-breaking updates unless THEY decide they want it. So, whatever auto-update mechanism MS puts in place, people will break it.
- nopassrecover 16y ago
  There's a massive difference between the Firefox auto-update (you're not launching until I'm installed then you're good) and the IE update (I'm going to make you reboot your PC, or nag you until you leave your PC idle for 15 minutes and I'll reboot losing your work for you. Oh yeah im tied into Windows Update so your PC as a whole might have random issues after reboot.)
percept 16y ago
They could shorten their release cycle but it wouldn't change the behavior of their largest customers. Consider a large organization that finally installed IE7. [Welcome to 2006!] I'm sure we'll have to deal with this for years to come (unfortunately), and neglecting corporate customers leaves a lot of money on the table.
- tptacek 16y ago
  A thousand times this. I have clients who are site-wide IE6 to this day. Ironically, Firefox worsened this problem, because all those clients also allow you to run Firefox (because IE6 barely works), but have apps that require IE, so (a) there's little incentive to upgrade (just use Firefox!) and (b) it's still likely that your first visit from a user there will be from IE6. IE7 is also much easier to work with than IE6, having had the semirecent pleasure of getting a jQuery-ish Rails app working on both.
  - grayrest 16y ago
    When chrome frame gets officially greenlighted, I'm immediately dropping all IE 6-8 support and campaigning as hard as I can at work for them to do the same.
deleted 16y ago
[deleted]

by niyazpk 16y ago

LaGrange 16y ago

They have auto-update. Usually disabled, because people somehow hate windows update, and corporate clients don't really want weird-application-breaking updates unless THEY decide they want it. So, whatever auto-update mechanism MS puts in place, people will break it.

nopassrecover 16y ago
There's a massive difference between the Firefox auto-update (you're not launching until I'm installed then you're good) and the IE update (I'm going to make you reboot your PC, or nag you until you leave your PC idle for 15 minutes and I'll reboot losing your work for you. Oh yeah im tied into Windows Update so your PC as a whole might have random issues after reboot.)

percept 16y ago

They could shorten their release cycle but it wouldn't change the behavior of their largest customers. Consider a large organization that finally installed IE7. [Welcome to 2006!] I'm sure we'll have to deal with this for years to come (unfortunately), and neglecting corporate customers leaves a lot of money on the table.

tptacek 16y ago
A thousand times this. I have clients who are site-wide IE6 to this day. Ironically, Firefox worsened this problem, because all those clients also allow you to run Firefox (because IE6 barely works), but have apps that require IE, so (a) there's little incentive to upgrade (just use Firefox!) and (b) it's still likely that your first visit from a user there will be from IE6. IE7 is also much easier to work with than IE6, having had the semirecent pleasure of getting a jQuery-ish Rails app working on both.
- grayrest 16y ago
  When chrome frame gets officially greenlighted, I'm immediately dropping all IE 6-8 support and campaigning as hard as I can at work for them to do the same.

deleted 16y ago

[deleted]