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 -
2: The mere *prospect* of a "defacto standard" is a very powerful social norm that discourages other effort in the space.
3 replies 0 retweets 15 likes -
3: And in practice, these "defacto standards" are more-or-less fads (or sometimes, solutions that work in a small domain).
2 replies 0 retweets 7 likes -
You can just say the names of the libraries, Yehuda
1 reply 0 retweets 1 like -
I promise that, at least this morning, I don't have much in mind. Maybe Backbone and Angular 1?
1 reply 0 retweets 0 likes -
More recently people occasionally have talked about React as being a defacto standard but there's a TON of competition and I'm not worried.
1 reply 0 retweets 1 like
Webpack is probably being overstated in this way. I'd be surprised if Webpack (at least resembling today's form) was dominant in 2020.
-
-
webpack is the current defacto for bundling. Saying that it being a canonical standard for bundling hasn't hurt people's attempt to innovate
1 reply 0 retweets 1 like -
Replying to @TheLarkInn @wycats and
See Fusebox, SystemJS, brunch, Bankai, InterlockJS, etc.
0 replies 0 retweets 1 like
End of conversation
New conversation -
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.