4 ms·
I work at a big tech MNC right now. We have apps that still require IE6. These are global apps. This company is also lauded for some amazing tech. Sometimes
by PakG1 15y ago
I work at a big tech MNC right now. We have apps that still require IE6. These are global apps. This company is also lauded for some amazing tech. Sometimes it's just difficult to allocate the necessary resources to update an app, and sometimes it's not worth it. In other cases, all the people who made the app just moved on and there's insufficient documentation to know how the app works. The code analysis process alone would be atrocious, and companies prefer to put pressure on revenue-generating initiatives, not maintenance initiatives, because if it ain't broke, don't fix it. And this is why all our computers still have IE6 installed.... @@ Fortunately, I've also got Chrome and Firefox on here because I have admin rights.
edit: Given how long mainframes have been around, is it really that much of a stretch to say that these kind of legacy web apps could still be around for a few years yet, if they're really integrated deep into an organization's processes?
- nl 15y agoWe have apps that still require IE6 Yep. Hence my comment "I think it is very, very unlikely that any non-client-Java webapp that runs in Firefox 3.x will break in any significant way in any future release" IE6-only (and IE-only) exist in the enterprise. That doesn't really impact on the Firefox upgrade strategy, since people don't use Firefox to access them. (Also, MS is slowly dropping support for operating systems supporting IE6. Enterprises are very reluctant to use unsupported operating systems.)
- ZeroGravitas 15y agoDidn't all that untouchable but still working mainframe stuff at some point get stuck in an emulated window, or screen-scraped into a web app, rather than have everyone stuck on terminals forever? It would be pretty ironic, but thanks to HTML probably not that hard, to be screen scraping an IE only web app to make it available to other web browsers.
- nl 15y agoLots of the IE6 only "webapps" use (in part at least) ActiveX controls. That's what makes them so hard to port - they aren't really webapps at all - just (old style, non .NET) client-server VB programs that happen to be deployed as ActiveX controls in a web page.
- pseale 15y agoAt some point IT will stop treating crusty enterprise web apps as web apps and start treating them as legacy enterprise apps that run in IE6. Instead of mandating everyone run IE6 from now to eternity, IT will provide a Citrix link to launch the crusty web app inside the controlled Citrix environment, and allow users to use more modern browsers by default. Or so we can hope.