4 ms·

IE6 was insanely bad. Later browsers worked somewhat.

by homero 7y ago

tracker1 7y ago
IE6 was pretty awesome when it was released... not having to support IE4.x and NN4.x when it hit sufficient market share was really nice. Eventually it became the next boat anchor. IE10-11 is the current boat anchor, and will probably cycle out within the next year. Already have internal apps with no IE support at all, and only the most recent Edge release. The perspective on outdated (insecure) browsers is becoming more broadly accepted.
- tty2300 7y ago
  Our enterprise app (not internal) has 80% of users on IE11 :/
  - tracker1 7y ago
    I'd suggest that comes down to the type of client/users you have... it's definitely not a common case. I'd also be willing to guess that most of those users also have a different browser installed. IE11 is pretty capable, but requires a lot of shims/shivs for modern code transpilation.
    - tty2300 7y ago
      The customers have weird IE security tools/firewalls and are not allowed to use anything else. For some reason they think that IE with very expensive tools to lock it down is more secure than a modern browser.
  - tjalfi 7y ago
    Did older versions of your app require IE? If so, their admins may have added your site to Enterprise Mode[0] so that it opens with IE. https://docs.microsoft.com/en-us/microsoft-edge/deploy/emie-to-improve-compatibility https://docs.microsoft.com/en-us/microsoft-edge/deploy/emie-...
    - tty2300 7y ago
      Nope, this is a modern react/es6 app that's only about 5 years old.
  - H1Supreme 7y ago
    How is that even possible? Are they not allowed to use something else?
    - tty2300 7y ago
      Yes. The 20% not on IE only left after we convinced their it department to switch.
  - robocat 7y ago
    Ouch. Our clients are businesses (less than 10000 employeees), and we still have 30% of userbase on Internet Explorer. We will soon be dropping IE9 and IE10 support. I suspect that we'll be supporting IE11 for another two years or so (even considering Windows 7 expiry!).
- octorian 7y ago
  > not having to support IE4.x and NN4.x when it hit sufficient market share was really nice. Ahh yes, the era when far too many web developers gleefully gave the finger to anyone not running Windows. I'm so glad those days are over.
  - SmellyGeekBoy 7y ago
    IE was available for Mac OS and desktop Linux wasn't really a "thing" in those days so I'm not sure who they were giving the finger to. BeOS users?
  - tracker1 7y ago
    By the time Firefox came out, it lined up with IE6 well enough to use the same code (W3C DOM) methods mostly. IE4.x and NN4.x support was horrific, and worse than IE6 when Google did what TFA mentioned. Dropping support for IE4/NN4 didn't mean not supporting other current browsers. When it was in the >90% market share, a lot of people did that though.
- deleted 7y ago
  [deleted]
bluedino 7y ago
We had a program that drew a map + path along the map... one customer complained about it taking 3 minutes to draw the path. Customer had an AMD 1400+ or something that was like 8 years old at the time. Threw my hands up in the air when they showed the system properties over a remote session. We installed Firefox 4 and it ran at a perfectly fine speed...

IE6 was insanely bad. Later browsers worked somewhat.

by homero 7y ago

IE6 was insanely bad. Later browsers worked somewhat.

IE6 was pretty awesome when it was released... not having to support IE4.x and NN4.x when it hit sufficient market share was really nice. Eventually it became the next boat anchor. IE10-11 is the current boat anchor, and will probably cycle out within the next year. Already have internal apps with no IE support at all, and only the most recent Edge release. The perspective on outdated (insecure) browsers is becoming more broadly accepted.

tty2300 7y ago
Our enterprise app (not internal) has 80% of users on IE11 :/
- tracker1 7y ago
  I'd suggest that comes down to the type of client/users you have... it's definitely not a common case. I'd also be willing to guess that most of those users also have a different browser installed. IE11 is pretty capable, but requires a lot of shims/shivs for modern code transpilation.
  - tty2300 7y ago
    The customers have weird IE security tools/firewalls and are not allowed to use anything else. For some reason they think that IE with very expensive tools to lock it down is more secure than a modern browser.
- tjalfi 7y ago
  Did older versions of your app require IE? If so, their admins may have added your site to Enterprise Mode[0] so that it opens with IE. https://docs.microsoft.com/en-us/microsoft-edge/deploy/emie-to-improve-compatibility https://docs.microsoft.com/en-us/microsoft-edge/deploy/emie-...
  - tty2300 7y ago
    Nope, this is a modern react/es6 app that's only about 5 years old.
- H1Supreme 7y ago
  How is that even possible? Are they not allowed to use something else?
  - tty2300 7y ago
    Yes. The 20% not on IE only left after we convinced their it department to switch.
- robocat 7y ago
  Ouch. Our clients are businesses (less than 10000 employeees), and we still have 30% of userbase on Internet Explorer. We will soon be dropping IE9 and IE10 support. I suspect that we'll be supporting IE11 for another two years or so (even considering Windows 7 expiry!).
octorian 7y ago
> not having to support IE4.x and NN4.x when it hit sufficient market share was really nice. Ahh yes, the era when far too many web developers gleefully gave the finger to anyone not running Windows. I'm so glad those days are over.
- SmellyGeekBoy 7y ago
  IE was available for Mac OS and desktop Linux wasn't really a "thing" in those days so I'm not sure who they were giving the finger to. BeOS users?
- tracker1 7y ago
  By the time Firefox came out, it lined up with IE6 well enough to use the same code (W3C DOM) methods mostly. IE4.x and NN4.x support was horrific, and worse than IE6 when Google did what TFA mentioned. Dropping support for IE4/NN4 didn't mean not supporting other current browsers. When it was in the >90% market share, a lot of people did that though.
deleted 7y ago
[deleted]

bluedino 7y ago

We had a program that drew a map + path along the map... one customer complained about it taking 3 minutes to draw the path. Customer had an AMD 1400+ or something that was like 8 years old at the time. Threw my hands up in the air when they showed the system properties over a remote session. We installed Firefox 4 and it ran at a perfectly fine speed...