A Business Case for Dropping Internet Explorer

Internet Explorer 11 (IE11) lags significantly behind modern browsers, creating substantial development challenges. Supporting this outdated browser consumes excessive time and resources, hindering productivity and increasing frustration. Is it financially sound to continue supporting IE11? Let's examine the case for abandoning it.

The Demise of Internet Explorer

IE11 development ceased in 2015. Microsoft Edge, its successor, offered significant improvements but initially fell short in web standards compliance. Microsoft is now rebuilding Edge using Chromium technology, further highlighting IE11's obsolescence. Microsoft itself has publicly acknowledged the perils of using IE11 as a default browser. The web has evolved beyond IE11's capabilities. The rapid pace of browser advancements since 2015, including CSS Grid and custom properties, renders IE11 incapable of supporting modern web features.

Lost Opportunities and Inefficiency

Since Microsoft deprecated IE11, the browser landscape has transformed dramatically. Numerous features supported by all major browsers except IE11 exist, a number set to grow with the Chromium-based Edge. While polyfills and transpilation can address some JavaScript compatibility issues, CSS features introduced in the last five years are entirely incompatible with IE11. This includes crucial advancements like CSS Grid, which simplifies responsive design, and other essential features like CSS custom properties and object-fit. The cumulative impact of these unsupported features makes IE11 a significant obstacle.

Supporting IE11 restricts the use of modern tools and frameworks. Frameworks like Vue 3 and MobX leverage JavaScript features untranspilable for IE11, impacting performance and API usability. Package management tools like Pika, requiring JavaScript modules, are also incompatible. Shadow DOM, a standardized web platform component, presents further challenges.

The High Cost of Support

The sheer number of unimplemented features in IE11 is only part of the problem. IE11's inherent complexity, inconsistency with web standards, and abundance of bugs add to the burden. Debugging in IE11 is notoriously difficult due to its primitive DevTools, consuming significant developer time. The definition of "good enough" support for IE11 can be subjective, leading to potential disagreements and increased technical debt. Maintaining functional compatibility requires extensive use of polyfills, transpilation, and prefixes, further increasing development effort.

Industry Trend: Abandoning IE11

Many leading websites, including YouTube, GitHub, and numerous others, have officially dropped IE11 support. Even Microsoft's own products have reduced IE11 support. Websites that ignore IE11 often redirect users to older versions or display warning banners. Forward-thinking companies prioritize modern web design and functionality, accepting the incompatibility with IE11.

The Significance of the New Chromium-based Edge

IE11 usage is declining, primarily due to the existence of legacy business applications incompatible with other browsers. The new Chromium-based Edge aims to resolve this by offering "Internet Explorer mode," ensuring compatibility with IE11-dependent sites. This allows companies to transition away from IE11 without losing access to legacy applications. The new Edge is becoming the default browser on Windows 10, further accelerating the decline of IE11.

Performance Implications

Transpiling JavaScript for IE11 negatively impacts performance. This process increases file sizes, extending download, parse, and evaluation times, particularly on low-end mobile devices. Differential serving can mitigate this, but it adds complexity. IE11's need for extensive polyfills adds unnecessary code to other browsers, further impacting performance. Modern CSS features like CSS Grid reduce reliance on bulky frameworks, improving performance, a benefit lost when supporting IE11.

The Financial Argument

The cost of maintaining IE11 compatibility should be weighed against the revenue generated from IE11 users. For most companies, the cost outweighs the benefit. Large corporations with substantial IE11 user bases might face a more complex decision. However, even for these companies, the improved performance and user experience gained by dropping IE11 support likely outweigh the potential revenue loss. Furthermore, supporting IE11 discourages innovation and hinders developer productivity.

Developer Experience and Recruitment

Developer satisfaction is crucial for recruitment and retention. IE11 debugging is a significant source of frustration for developers. Surveys consistently rank IE11 support as a major pain point. By eliminating this frustration, companies can improve developer morale and attract top talent.

Accessibility for IE11 Users

Users encountering issues with a website on IE11 can typically access it using other devices or browsers. Microsoft Edge is pre-installed on Windows 10, providing a readily available alternative.

Cross-Browser Testing

A robust cross-browser testing process is essential. Focusing on popular browsers is more cost-effective than catering to IE11.

The Decision to Drop IE11 Support

The decision to drop IE11 support depends on individual website analytics. Global browser usage varies significantly. Regularly reassessing analytics, especially after the release of the new Edge, is crucial.

The above is the detailed content of A Business Case for Dropping Internet Explorer. For more information, please follow other related articles on the PHP Chinese website!