Why WordPress’ use of polyfill.min.js is irresponsible.
WordPress has been my go-to CMS for, like, ever (if I can use my teenage voice.)
There was a time when the platform was dedicated to evolving the web, not just being the most popular CMS out there, but actually making the web better. One could say that it became the best CMS precisely because of this. It was fairly easy to use, open-source and really extendible.
Hashtag lame, yo.
The modern web is about performance. Making a website easy to build, only to make that build difficult for people to consume, is not making the web better. Thus, WordPress can be said to now be making the web worse.
But these things can be somewhat easily overcome. It’s theoretically possible, though a lot more work than in the Classic Editor days, to rewrite, trim down and otherwise just optimize the CSS part. So problem solved, eh?
Until you get to the inclusion of polyfill.min.js. Woocommerce seems to love including this file as well, but Woocommerce loves to include every file it possibly can. It must be some type of challenge over there these days.
All of that said, the concept that the team at WP would use polyfill.js because modern browsers need it is just a lie.
They’re using it because it’s easier. They’re creating a new Netscape vs. Internet Explorer battle, which doesn’t exist, and then running with it. Even the folks behind WP don’t know exactly what polyfill.min.js is doing. That’s scary.
It’s hard to comment too much on this without knowing what exactly lurks inside wp-polyfill; I can’t seem to find an authoritative list of what it includes, nor any sort of readable, adequately commented source. source
I was around in 2001, so trust me, the current browser situation is awesome. Please WordPress, don’t ruin it by making an entire new generation of developers think this polyfill idea is acceptable.
Up Next: How to Embed a Spotify Playlist