But there is no excuse for browsing the public web with IE6 anymore. Especially if there's a modern browser installed side by side with IE6.
Ideally, a firewall should be set up so that IE6 can't access anything outside of 10/8, 172.16/12, 192.168/16, and localhost.
I just really don't have any sympathy for you. It's not anything approaching hard these days. These days, you just write everything in a compiles-to-javascript language it figures out the browser compatibilities for you. That shit didn't EXIST. You were considered an ASSHOLE if you did anything with JavaScript.
Hopefully, one day I will be the crotchety old man complaining about how the new kids never had to worry about IE8 issues.
After all, that's the whole point of progress. How dared our ancestors complain about working 12 hours a day in dangerous coal mines when their own ancestors worked 16 hours a day under even more dangerous conditions? IE4 vs. NN4 was trivial by comparison with that, but the general principle holds.
You've also got https://chrome.google.com/webstore/detail/ie-tab/hehijbfgiek...
No, two things:
i) It's not about being stubborn. Companies have invested a lot of money and time to run critical applications. Even if they have the money the risk of migration is high.
ii) They have already migrated to newer browsers! they just run IE6 side by side with modern browsers using application virtualization.