[batrat]

Users are dumb thats why. We literally have to make 4-5 shortcuts with iexpore.exe website.net and another one with chrome.exe website2.net and rename them accordingly. Some vendors have their web app work only with firefox and an old version like 20+ /:.

Not to upset any dev but really trying to put some fancy stuff and a bunch of frameworks in a piece of software that does one thing and has to work 24/7 is really a bad ideea.

[mattmanser]

There's good reasons why these exist, and it's got zero to do with dev competence.

In 2005 your employer asks for internal app, says you've got to use kendo or some such UI framework. Or maybe they want an autocomplete drop-down and you picked one that in the future will turn out to be not standards compliant. Or you were asked to use the stylesheet from another project to get them to look the same and that's not compliant. But you don't even know, as it only has to work on IE8 as that's all that's available to your users. You make it. It works fine.

Fast forward to 2015, no-ones touched the app in 10 years, the SVN server the code was on has been thrown away, and it's either rewrite the whole thing or force everyone to keep on using IE8.

That's what generally happened, not dev incompetence.

[syshum]

>Users are dumb thats why. We literally have to make 4-5 shortcuts with iexpore.exe website.net and another one with chrome.exe website2.net and rename them accordingly.

Edge in Enterprise Mode solves this as you provide edge with a list of sites that need IE, then Edge will automatically open those sites in IE Tab (or in previous versions of Edge, redirect the user automatically to IE)