3 ms·

That doesn't change that IE is still needed for those old applications. So the best case scenario is running whatever new browser like Firefox, Chrome, etc, an

by PakG1 14y ago

That doesn't change that IE is still needed for those old applications. So the best case scenario is running whatever new browser like Firefox, Chrome, etc, and running IE6 alongside. Ditch IE6 only after the old apps have been replaced completely.

melling 14y ago
I'm a little confused. Why is there IE6 lockin? Apps weren't built so they could at least be easily upgraded to IE8? Some testing is required and no one wants to do the work? My memory isn't that hazy. What happened was that people said the software only had to run in IE6 and Netscape wasn't important. Writing "good" web software wasn't important. Simply support Microsoft's IE6 and you're done. If you're still stuck on IE6/IE7 it really is your own fault.
- saraid216 14y ago
  michael_miller explained it adequately above: 1) IT departments are massively conservative (and this is not an intrinsically bad thing) 2) A lot of apps were built specifically for IE6. They still work with IE6. Many times they only work with IE6. 3) It hasn't been made worthwhile to upgrade. > If you're still stuck on IE6/IE7 it really is your own fault. A lot of us web developers have decided to just say, "Fuck it," and stop supporting IE6. If it works, cool; if it doesn't, we don't care. This is a luxury available to those of us who have clients who aren't supported by the aforementioned IT departments. Some of us are still required to support IE6 because we have clients who we can't drop and refuse to move off, and we don't have the leverage to persuade them otherwise.
  - hellweaver666 14y ago
    For some companies it doesn't make sense to drop support for IE6. I work for a company who's product is sold completely online. If we dropped support for IE6 we would loose hundreds of thousands (if not millions) of dollars a year. Sure it's a tiny fraction of our business, but it's a considerable amount of money and pretty much covers the wages of our entire web development team.

by PakG1 14y ago

melling 14y ago

I'm a little confused. Why is there IE6 lockin? Apps weren't built so they could at least be easily upgraded to IE8? Some testing is required and no one wants to do the work? My memory isn't that hazy. What happened was that people said the software only had to run in IE6 and Netscape wasn't important. Writing "good" web software wasn't important. Simply support Microsoft's IE6 and you're done. If you're still stuck on IE6/IE7 it really is your own fault.

saraid216 14y ago
michael_miller explained it adequately above: 1) IT departments are massively conservative (and this is not an intrinsically bad thing) 2) A lot of apps were built specifically for IE6. They still work with IE6. Many times they only work with IE6. 3) It hasn't been made worthwhile to upgrade. > If you're still stuck on IE6/IE7 it really is your own fault. A lot of us web developers have decided to just say, "Fuck it," and stop supporting IE6. If it works, cool; if it doesn't, we don't care. This is a luxury available to those of us who have clients who aren't supported by the aforementioned IT departments. Some of us are still required to support IE6 because we have clients who we can't drop and refuse to move off, and we don't have the leverage to persuade them otherwise.
- hellweaver666 14y ago
  For some companies it doesn't make sense to drop support for IE6. I work for a company who's product is sold completely online. If we dropped support for IE6 we would loose hundreds of thousands (if not millions) of dollars a year. Sure it's a tiny fraction of our business, but it's a considerable amount of money and pretty much covers the wages of our entire web development team.