TC39 is not a responsible entity. They are not to be trusted
-
-
@wycats@slightlylate@BrendanEich@domenic In past, browsers did "just ship" which led to (de facto and terrible) fast cross-browser uptake -
@DavidBruant@wycats@BrendanEich@domenic : you gloss over the bit where, on the back of that, we got a winner of a platform. Not all bad. -
@slightlylate@DavidBruant@BrendanEich@domenic not all history repeats itself. Not all discussion is bad. -
@wycats@DavidBruant@BrendanEich@domenic : so ship, godammnit. FYI, it's how we shut down TC39 pinhead-angel-counting on Promises. -
@slightlylate No, that's not true. V8 promises did not match cowpath. ES6 got back on track via TC39 arguing.@wycats@DavidBruant@domenic -
@slightlylate +here: http://esdiscuss.org/notes/2014-01-30#promises-discussion …. What V8 shipped didn't set the standard or even pave the cowpath.@wycats@DavidBruant@domenic -
@slightlylate Promises had too many mega-threads and cooks, Promises/A+ vs. Monadic, false consensus in 9/13.@wycats@DavidBruant@domenic - 18 more replies
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.