5 ms·

> start putting up banners that say "our website does not work with your browser, please switch to Chrome" That's how IE 6 was killed.

pjmlp 1mo ago
It was killed by a lawsuit, mostly. Also FE devs using all new Chrome shinny APIs, and their Electron junk are also to blame, and they aren't going to throw their toys away.
- tentacleuno 1mo ago
  If nothing else, I really do hope that the greater AI usage leads to more adoption (and hopefully interest) of native frameworks.
  - pjmlp 1mo ago
    If only, everyone brags about Claude and Fable, yet they can't do anything better than Electron and React for TUIs.
dspillett 1mo ago
The final death of IE6 was because corporates finally stopped using it⁰ and the reason for that had nothing to do with sites/apps refusing to work. If we'd said "we don't support IE6" they'd either say "the contract we signed years ago somehow says otherwise" or "fair enough, we'll use someone else's solution then". What killed it was IE6 not supporting TLS1.0 out of the box or TLS1.1+ at all, and that started to make them fail external audits. After years of telling them IE6 was holding us back implementing best-practise security on their instances of our apps¹ and being ignored because doing anything about it their side was too much hassle, external auditors started refusing to give them relevant certificates & such because of their systems not being up to best practise (or even good practise by that point!) and suddenly they made the effort to no longer have anyone in their orgs using IE6. -------- [0] source: I was working on software serving the banking industry (customer facing & investment sides, not trading) around that time and years either side [1] Even having annual conversations like: ! The pen test results say you should disable anything below TLS1.0 (and later 1.1), and you haven't. Please do. ? Are you sure? We'd *really* like to, as we've repeatedly mentioned, but that will block your IE6 users. ! Yes! You must follow the recommendations! ? Excellent. Done. [a short time passes] ! Your application is broken for some of our users! ? Yep. They are using IE6 without TLS enabled. ? Either you need to upgrade their configurations or tell us, in writing please, to break from best practise and reenable the older protocols. [another short time later] ! Please reenable the older protocols.
- tomkarho 1mo ago
  I'd like to think this conspiracy at least contributed: https://blog.chriszacharias.com/a-conspiracy-to-kill-ie6 https://blog.chriszacharias.com/a-conspiracy-to-kill-ie6 Unless it's all fud in which case I shall archive this under headcanon.
  - dspillett 1mo ago
    Oh that certainly did the trick for home users, but I was having to deal with IE6 for our clients (at least one of them was IE6 only), as were people I knew working in or otherwise supporting other corporate environments, for several years after that. Some management types might have even seen YouTube potentially blocking IE6 users as an advantage for keeping with IE6 to save bandwidth on their creaking external network links!

pjmlp 1mo ago

It was killed by a lawsuit, mostly. Also FE devs using all new Chrome shinny APIs, and their Electron junk are also to blame, and they aren't going to throw their toys away.

tentacleuno 1mo ago
If nothing else, I really do hope that the greater AI usage leads to more adoption (and hopefully interest) of native frameworks.
- pjmlp 1mo ago
  If only, everyone brags about Claude and Fable, yet they can't do anything better than Electron and React for TUIs.

dspillett 1mo ago

The final death of IE6 was because corporates finally stopped using it⁰ and the reason for that had nothing to do with sites/apps refusing to work. If we'd said "we don't support IE6" they'd either say "the contract we signed years ago somehow says otherwise" or "fair enough, we'll use someone else's solution then". What killed it was IE6 not supporting TLS1.0 out of the box or TLS1.1+ at all, and that started to make them fail external audits. After years of telling them IE6 was holding us back implementing best-practise security on their instances of our apps¹ and being ignored because doing anything about it their side was too much hassle, external auditors started refusing to give them relevant certificates & such because of their systems not being up to best practise (or even good practise by that point!) and suddenly they made the effort to no longer have anyone in their orgs using IE6. -------- [0] source: I was working on software serving the banking industry (customer facing & investment sides, not trading) around that time and years either side [1] Even having annual conversations like: ! The pen test results say you should disable anything below TLS1.0 (and later 1.1), and you haven't. Please do. ? Are you sure? We'd *really* like to, as we've repeatedly mentioned, but that will block your IE6 users. ! Yes! You must follow the recommendations! ? Excellent. Done. [a short time passes] ! Your application is broken for some of our users! ? Yep. They are using IE6 without TLS enabled. ? Either you need to upgrade their configurations or tell us, in writing please, to break from best practise and reenable the older protocols. [another short time later] ! Please reenable the older protocols.

tomkarho 1mo ago
I'd like to think this conspiracy at least contributed: https://blog.chriszacharias.com/a-conspiracy-to-kill-ie6 https://blog.chriszacharias.com/a-conspiracy-to-kill-ie6 Unless it's all fud in which case I shall archive this under headcanon.
- dspillett 1mo ago
  Oh that certainly did the trick for home users, but I was having to deal with IE6 for our clients (at least one of them was IE6 only), as were people I knew working in or otherwise supporting other corporate environments, for several years after that. Some management types might have even seen YouTube potentially blocking IE6 users as an advantage for keeping with IE6 to save bandwidth on their creaking external network links!