When's the last time a JS library was called a defacto standard and it was still the overwhelmingly dominant solution 3 years later?
-
-
Replying to @wycats
We have data goong back to 2010, but since then, I don’t think so. Anecdotally, Jquery definitely was dominant for at least 5 years, iirc.
2 replies 1 retweet 18 likes -
Watch this space for a fascinating tech talk by
@seldo2 replies 0 retweets 5 likes -
1: Sweet! The point I want to make (if the data complies) is that talk of "defacto standards" is corrosive to progress.
3 replies 2 retweets 18 likes -
The data is REALLY mixed in support of that conclusion.
1 reply 0 retweets 1 like -
What are some good counterexamples? I have moment.js, lodash and d3.
1 reply 0 retweets 3 likes -
By a counter example, you mean: a very popular library that stayed popular for 5 years?
1 reply 0 retweets 0 likes -
Yes, and where competition wasn't necessary to address deficiencies.
2 replies 0 retweets 0 likes -
Express has been astonishingly durable.
1 reply 0 retweets 9 likes -
Also many of the lower level, early libraries have no competition because they are just great. async, qs, and mkdirp aren't going anywhere.
2 replies 0 retweets 3 likes
async is going somewhere ;)
-
-
I think I'd consider mkdirp a part of the defacto stdlib, which is probably a little different. For mkdirp
@substack was right.0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.