ES6 is a language, a standard library is a little bit more than that.
The absurdity of the amount of third party packages, utilities, snippets, slightly different implementations and so on that you find on npm might be a result of the lack of a common standard library.
That's what I meant.
This was talked about in an article on Medium I read recently: hackernoon.com/whats-really-wrong-...
Thanks, I've read it. Well, I think everyone would agree on the practicality of a common and official standard library. The hard thing would be to find who's going to take lead on that. You need at least the support of the TC39 committee, the big browser vendors and so on. The issue is that most successful open-source projects have either a BDFL or a cohesive core team, usually there since the beginning, not 20 years after the creation of the language. I hope time and possibly some fed up big players in the community will result in a real conversation being started.
Nobody forbids you to write your own package "is true", it just probably shouldn't be included automatically by hundreds of packages 😅
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.