I need a compelling case for why we should not support IE11. Apparently 10% of our user base uses it and "it fucking sucks and breaks all the new shit you want me to do" is not an answer. And a possible HR violation.

Edge chromium

Its not supported by ms itself. It has security holes in it. It costs more in the end, since modern browser have better javascript parsers that help you writing good code (modules).

@stop
This. And realistically, why would you *keep* supporting it. Anyone can install chrome and applications that just have to have it, can still use it.

It's going away whether they want it to or not, so future proof your shit [insertcompanyhere]

This reminds me of the kill IE6 and IE8 movements.

It took years to drop support for them properly even after MS dropped issuing security updates.

Being browser agnostic while using new frameworks just creates an oxymoron and increases development costs to maintain backwards compatibility.

If you were still using JQuery and Bootstrap then fuck it, shits going to work in any browser, but I have my doubts with this being the case here.

Just so everyone is actually clear, MS has not dropped support for IE11 yet as it is tied to the OS lifecycle.

It is being fazed out with Edge and now Edgium, but it will continue to stay alive in the background for the foreseeable future.

---
The latest version of Internet Explorer will continue to follow the component policy. This means that it follows the lifecycle of the Windows operating system on which it is installed. Focusing support on the latest version of Internet Explorer for a supported Windows operating system is in line with industry standards.

https://support.microsoft.com/en-us...

You can "support" IE11 by having it redirect to a page to install Firefox.

@momad true, but this is a web app and our load times on ie11 suck because it fucks up our lazy loading.

@C0D4 apparently some of the more modern jquery stuff doesn't work in ie11. Which is a part of the problem. Though, question, do React and Angular work in ie11?

@momad windows 7 sp1 and 8.1 are out of support, so on desktop no version is in support.

@projektaquarius
Angular works back to 9, sans compatability mode. Angular material controls do as well.

Reported user market share of IE11 is too low too justify the time and cost of researching fixes and patching (read "hacking") code to make it work correctly. It's often a bad business decision.

Of course, if you guys are still at 10%, that's probably not low enough to use this excuse. It's closer to 2% worldwide depending on the source.

Just make a case of how much longer it will take to develop and maintain support for browser that is reaching end of life. I would honestly quit if they forced me to develop for ie.

@jdebs it's analytics results but I figure that may be case enough.

it fucking breaks and does all the shit you want me to suck

@electrineer tried that. Unfortunately.

Progressive enhancement anyone? The pretty easy solution is to not guarantee that all bells and whistles work with IE11.

If however your whole website doesn't even display because you're a fucktard so high on JS crack that you have forgotten how to write websites, then IE11 maybe isn't part of the solution, but you're definitely part of the problem.

@Fast-Nop
I need to borrow your ladder to argue with business owners. I am beyond tired of hearing petulant wheezing from non-technical decision makers like, "I don't understand why this can't work in [mosaic], I love [mosaic]." To which I can only internally reply, "that's obvious."

@SortOfTested

If you have not seen this you might appreciate this:

https://youtube.com/watch/...

@Demolishun
A true classic

@SortOfTested In half of the cases, the customer stops wanting cosmetic polyfills on IE11 when they see the price tag for no benefit, and the other half doesn't even belong on production websites in the first place because most websites are already bloated, overengineered and then even badly implemented crap anyway.

@Fast-Nop oh it's a terrible website. Not because of anything any one person wrote, but because the entire thing was built in a series of 2 week deadlines with management deciding that a feature that kinda works in 2 weeks is better than a robust, extendable feature in 4 built atop a CMS with little to no helpful documentation and hacky css put on top of it to handle CMS editors with too much power. It physically hurts me to work on this thing.