@fishrock123 @rvagg btw i don't really want to have this discussion if there's just going to be dismissal
-
-
Replying to @Fishrock123
@sebmck There’s a a forward motion of filling ECMA with everything possible. 1) because that’s effectively what TC39 exists for now (..)1 reply 0 retweets 0 likes -
Replying to @Fishrock123
@sebmck (..) 2) because browsers are terrible at effectively sharing user code, so to decrease load times, it is “required”.2 replies 0 retweets 0 likes -
-
Replying to @Fishrock123
@fishrock123 oh right, about the inclusion of things in the language to reduce load bloat. not everything is polyfillable, not even syntax.1 reply 0 retweets 0 likes -
Replying to @Fishrock123
@sebmck (..) Why would we ever implement an async/await API using those? That’s like telling users their mission-critical apps (..)1 reply 0 retweets 0 likes -
@fishrock123 the overhead of the actual asynchronous primitives are 10x slower atm but they won't be in the future
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.
he/him 