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
I suspect one of the biggest factors in adoption/retention is how closely a library resembles the code you already know.
1 reply 0 retweets 0 likes -
Replying to @brotherdavidson @wycats
For example Lodash is pythonic and rubyish. Backbone.View’s API is jQuery-ish. Anything Promise A+ is very easy to reason about.
1 reply 0 retweets 0 likes -
Replying to @brotherdavidson
You'd be surprised how many people said Promises/A+ was weird and much harder to understand than callbacks.
3 replies 0 retweets 0 likes -
Replying to @wycats @brotherdavidson
Yehuda Katz 🥨 Retweeted Mikeal Rogers
Example: https://twitter.com/mikeal/status/444157115238604800 …
@mikeal has recanted but this was a popular view at the time.Yehuda Katz 🥨 added,
3 replies 0 retweets 0 likes -
Replying to @wycats @brotherdavidson
i still don't think raw promises are easier than callbacks :) async/await was a game changer.
4 replies 0 retweets 7 likes
I agree! Screenshot is from a talk I gave in 2014 describing the glorious async function future.pic.twitter.com/5AojW1Axlu
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.