3 ms·
Was struggling with legacy IE6 support-hacks too once while building healthcare webapps. In that field, it was more because hospital IT admins lock everything d
by floatrock 7y ago
Was struggling with legacy IE6 support-hacks too once while building healthcare webapps. In that field, it was more because hospital IT admins lock everything down and upgrading stuff very much falls under the "if it ain't broke, don't fix it" mantra.
We too got fed up with all the IE6-specific hacks we had to maintain. One day on the login page, we added a "IE6 might be a HIPAA violation, please upgrade your system" banner. It was technically true... the browser was well past its end-of-life support and was acquiring a running list of unpatched security holes.
Our analytics showed the remaining holdouts upgraded their systems over the next few months.
- kevan 7y agoA bit more recently (I hope), PCI requirements helpfully forced our hand to stop supporting IE8.
- chewmieser 7y agoThat was a scary transition for us, since we did have quite a few legacy browsers regularly accessing our site - we guaranteed support for IE7+ at that time. Extremely thankful for it though, our management wouldn't have made that decision without the push.
- titanomachy 7y agoThe "ain't broke don't fix it" attitude makes sense when you consider e.g. a medical scanning device with a Windows-based console. Those things generally live offline and get tested and approved as an integral unit, including the exact software loaded on them at the time. Unfortunately, that attitude in healthcare leaks to things which _are_ connected to the internet, and you get disgraceful incidents like the hacking of Britain's NHS in 2017.
- Quarrelsome 7y agowhere the guy that helped stop the attack got locked up by the US feds for stuff he did in his teens while visiting a security conference. They've kept him locked up on anything they can drum up for the purposes of flipping him. Has it been two years already?