4 ms·
I wonder how many of these ancient legacy systems are content to stay on IE because everyone coddles them with support? Chicken and the egg kind of thing. Why i
by fortyseven 7y ago
I wonder how many of these ancient legacy systems are content to stay on IE because everyone coddles them with support? Chicken and the egg kind of thing. Why invest the time and money to modernize if devs will bend over backwards to keep them on life support?
- efdee 7y agoNot sure. At least in my experience, the people demanding that their apps keep working on IE11 are not the people who care about what framework we use to build the apps.
- beart 7y agoMore likely it's because no one wants to pay to upgrade the hundreds of barely supported in-house apps their company has that only run on IE 11 in compatibility mode.
- karatestomp 7y agoThe people making the decision judge their personal risk to be higher if they initiate the change than if they stick with the status quo, even with the chance that it causes a major breach—they might not get blamed for that, anyway. Same as most business decisions.
- wstuartcl 7y agoIt depends on your user base. Sometimes you must coddle because the users are still high on your active user reports and not supporting them is a choice between killing off that user base or keeping them. For instance if your business model is to sell to/support highly regulated industries or govt users you are effectively forced to support their current user base configs or lose that share of the market because the choice for them is deal with a huge change to their requirements and support (which move at a glacial rate) OR chose a different vendor for your provided service.
- sebazzz 7y agoEspecially because the ones to make that call may not know that their business apps support other web browsers. We sell some tools, which also work on IE11 but definitely on other web browsers. Do our clients know that? I wouldn't know, and wouldn't count on it.