# Dropping IE8 Support: Consequences for JavaScript

DevFeed: [Dropping IE8 Support: Consequences for JavaScript](<https://devfeed.tech/articles/dropping-ie8-support-consequences-for-javascript-27943.md>)

Original publisher: [Read original article](<https://tech.trivago.com/post/2016-06-01-dropping-ie8-support-consequences-for-javascript/>)

Author: Patrick Gotthardt Follow

Published: 2016-06-01T00:00:00Z

Content type: article

Language: en

Sources: [Trivago](<https://devfeed.tech/sources/trivago.md>)

Topics: [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Internet Explorer](<https://devfeed.tech/topics/internet-explorer.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>)

Tags: [babel](<https://devfeed.tech/tags/babel.md>), [browser](<https://devfeed.tech/tags/browser.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [internet-explorer](<https://devfeed.tech/tags/internet-explorer.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [libraries](<https://devfeed.tech/tags/libraries.md>), [performance](<https://devfeed.tech/tags/performance.md>)

## AI overview

The article describes trivago's experience after dropping Internet Explorer 8 support. It reports that the change allowed developers to update dependencies such as jQuery, core-js, and Babel, adopt newer JavaScript standards, reduce testing and debugging overhead, remove compatibility workarounds, and improve performance in other browsers.

## Source excerpt

When people hear about dropping support for a certain Internet Explorer version, they mostly think of all the CSS hacks and workarounds that could be removed as a consequence. However, dropping support for IE8 can have subtle, but profound effects on your JavaScript.