A lot of things in ES6 cause bloat imo. We don't need 6 different ways to do async.
-
-
Replying to @yoshuawuyts
@yoshuawuyts Generators and Promises have different use-cases. You should try out Ember, they use Promises extensively to deal with async.1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts@JonKoops async/await relies heavily on promises. It’s like you said we don’t need XMLHttpRequest as there’s jQuery.ajax.1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts@JonKoops Promises introduce absolutely no new keywords.1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts@JonKoops What would you prefer? To freeze and not change anything?1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts@JonKoops Gradual standardizing would take ages and changes are long overdue. Besides, experimental impls are already happening1 reply 0 retweets 0 likes
-
-
Replying to @yoshuawuyts
@yoshuawuyts@m_gol A lot of features added actually improve te accessability. I.e. classes and lexical this bindings.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.