Modern engines are cool with long proto chains.
-
This Tweet is unavailable.
-
-
This Tweet is unavailable.
-
-
This Tweet is unavailable.
-
Replying to @treshugart @TheLarkInn
We started years earlier by including a growing set of FW engineers (myself included). Node came around after their community got over rage.
1 reply 0 retweets 0 likes -
Much of ES6 was only possible because of changed committee composition. Still took too long, tho.
1 reply 0 retweets 0 likes -
Consider: we proposed async/await in 2011! Classes dragged for years. New process helps (and, in part, a result)
1 reply 0 retweets 1 like -
Replying to @slightlylate @treshugart
FWIW i see why ya'll jumped on async await, implement so fast, was to save all the bloat from generator getting transpiled down ezwin 4 perf
1 reply 0 retweets 1 like -
Which of course is EZwin for people using the web etc.
1 reply 0 retweets 1 like
We proposed Promises ("Deferred" and "Futures") *explicitly* to get to syntax for the (async/await). Circa '11 committee didn't grok need 
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.