> Adding a transpilation step to extend support to older browsers comes with almost no cost to time or maintainability They may be simple concepts, but there's

> Adding a transpilation step to extend support to older browsers comes with almost no cost to time or maintainability They may be simple concepts, but there's definitely still an added cost with transpilation and minification steps. If you work with Babel long enough you'll encounter scenarios where the transpiling didn't quite work as expected and breaks in-browser. When you're debugging minified code in-browser using source maps, it's not all that uncommon to get different line numbers and stack traces than you get when loading up the original unminified source. I can recall a number of occasions where I had to deploy unminified source for in-browser debugging because the source maps were obfuscating the real error. https://www.joelonsoftware.com/2002/11/11/the-law-of-leaky-abstractions/ https://www.joelonsoftware.com/2002/11/11/the-law-of-leaky-a...