> This week, one of the most critical pieces of web software [..] Nah, it’s not critical anymore, assuming it ever was. It’s a pest that finds its way into you

> This week, one of the most critical pieces of web software [..] Nah, it’s not critical anymore, assuming it ever was. It’s a pest that finds its way into your code and you have to expend energy to get rid of it. First off, it’s huge. Check this out: https://bundlephobia.com/package/core-js@3.28.0 https://bundlephobia.com/package/core-js@3.28.0 How many copies of that do you have in your bundle? Second, it’ll replace the native implementations of things like Promises and iterators with its own slower and bloated implementations in the name of compatibility, but is it even necessary anymore? IE11 is dead and the rest of the browsers get updated automatically. There might still be stragglers in the corporate world, but honestly I’d rather deal with any issues that come up over adding core-js “just in case”. I’ve also seen it cause issues due to said replacing of native functionality. Maybe it’s time we moved on.