3 ms·
Why force all your users to download transpiled ES5, just to accommodate IE11 dinosaurs? Not to mention all the issues you'll have if you try to use CSS Flex o
by depressedpanda 7y ago
Why force all your users to download transpiled ES5, just to accommodate IE11 dinosaurs?
Not to mention all the issues you'll have if you try to use CSS Flex or Grid.
Support IE11 only if you absolutely must, is my advice, and do that with differential serving:
https://philipwalton.com/articles/deploying-es2015-code-in-production-today/ https://philipwalton.com/articles/deploying-es2015-code-in-p...
https://calendar.perfplanet.com/2018/doing-differential-serving-in-2019/ https://calendar.perfplanet.com/2018/doing-differential-serv...
- tracker1 7y agoAgreed, but I'd just assume avoid dual builds and targets at this point... a project I'm working on started with IE11 support and dual build targets, but broke in IE11 about 3 weeks in, so changed the "legacy" build mode to a page noting the requirement for a modern and secure browser.