2 ms·
This is how things have worked in the JS community for a long time. It's easy to say that new library X "is already used by Y and Z" which have millions of down
by ricardobeat 5y ago
This is how things have worked in the JS community for a long time. It's easy to say that new library X "is already used by Y and Z" which have millions of downloads, when you're the author of X, Y and Z and have a following. The library gets instant adoption, collaborators and good search rankings.
It's not always bad, but it stifles creativity and I believe has caused us to be stuck with libraries just because "they are popular and well-maintained" versus finding the actual ideal solution, the React ecosystem being a strong example of that. Not to mention that, contrary to what you would expect, the larger the company, the more often decisions will be made based on github star count, almost completely ignoring technical merit.
</rant>