4 ms·

>Why did developers and software engineers hate IE so much? Because IE was seriously outdated, lacking support for cutting-edge web APIs and technologies enabli

>Why did developers and software engineers hate IE so much? Because IE was seriously outdated, lacking support for cutting-edge web APIs and technologies enabling the modern websites and web apps we use today. Nonsense. The almost universal contempt for Internet Exploder amongst web developers had nothing to do with lack of support for cutting edgw APIs. It was because Internet Exploder refused to follow basic web standards and was stuffed it full of proprietary and non-standard rendering quirks. This meant you could guarantee that any website you designed and that you ensured followed web standards and rendered perfectly on every browser known to man would either break or display completely differently on IE. So you had to then pollute your lovely clean code with countless ugly hacks and conditionals just to ensure your site rendered the same on IE as it did everywhere else. That was why every web developer not working in a Microsoft bubble loathed that browser.

Dma54rhs 5y ago
Safari doesn't even work on other platforms, my office doesn't test or fix their specific bugs anyway. Good riddance.
alserio 5y ago
I still have to support IE11 and the fact that it doesn't support modern API its one of the reasons I hate it with passion. Something like not supporting css variables is seriously limiting. As second place I'll put the unusable dev tools. Spec compliance is more of a problem for css than js. I concede that with previous IE iteration the problem was much more worse.
- G3rn0ti 5y ago
  At least it has dev tools. IE6 didn’t. So every time JS failed I had to alert myself into the heart of the problem…
  - alserio 5y ago
    I'm grateful to the previous generation of web dev, and their suffering to avoid us younger generations their pain.
- deergomoo 5y ago
  I agree, but I will say that if your site doesn't rely on newer CSS features, IE11 is still surprisingly easy to deal with. A whole lot of cutting-edge JavaScript can be polyfilled/transformed to work on IE11 (automatically in most cases, with something like Babel), and the module/nomodule pattern can stop that polluting your bundles for modern browsers. It also has decent flexbox support (just a few oddities easily worked around IIRC), although its grid implementation is incomplete and uses an older version of the spec that in most cases just isn't worth the effort.
The_Colonel 5y ago
> The almost universal contempt for Internet Exploder amongst web developers had nothing to do with lack of support for cutting edgw APIs. It was because Internet Exploder refused to follow basic web standards and was stuffed it full of proprietary and non-standard rendering quirks. Nope. IE6 was the most standards-compliant browser out there in 2001. The problem was that it did not move from its 2001 state for many years (development was dropped).

Dma54rhs 5y ago

Safari doesn't even work on other platforms, my office doesn't test or fix their specific bugs anyway. Good riddance.

alserio 5y ago

I still have to support IE11 and the fact that it doesn't support modern API its one of the reasons I hate it with passion. Something like not supporting css variables is seriously limiting. As second place I'll put the unusable dev tools. Spec compliance is more of a problem for css than js. I concede that with previous IE iteration the problem was much more worse.

G3rn0ti 5y ago
At least it has dev tools. IE6 didn’t. So every time JS failed I had to alert myself into the heart of the problem…
- alserio 5y ago
  I'm grateful to the previous generation of web dev, and their suffering to avoid us younger generations their pain.
deergomoo 5y ago
I agree, but I will say that if your site doesn't rely on newer CSS features, IE11 is still surprisingly easy to deal with. A whole lot of cutting-edge JavaScript can be polyfilled/transformed to work on IE11 (automatically in most cases, with something like Babel), and the module/nomodule pattern can stop that polluting your bundles for modern browsers. It also has decent flexbox support (just a few oddities easily worked around IIRC), although its grid implementation is incomplete and uses an older version of the spec that in most cases just isn't worth the effort.

The_Colonel 5y ago

> The almost universal contempt for Internet Exploder amongst web developers had nothing to do with lack of support for cutting edgw APIs. It was because Internet Exploder refused to follow basic web standards and was stuffed it full of proprietary and non-standard rendering quirks. Nope. IE6 was the most standards-compliant browser out there in 2001. The problem was that it did not move from its 2001 state for many years (development was dropped).