(for timing, engines landed ES6 minus modules in mid-2016)
-
-
Show this thread
-
ES2017 included async functions and shared memory and atomics. Hardly a failure of cross cutting concerns.
Show this thread -
ES2018 included async iteration, and a bevy of new class features made it to Stage 3 during the ES2018 time frame. Those class features are under active development in engines[1][2] [1] https://bugs.chromium.org/p/v8/issues/detail?id=5367 … [2] https://bugs.webkit.org/show_bug.cgi?id=174212 …
Show this thread -
JavaScript is already a big language, and adding big, cross cutting features at a faster pace than this does not strike me as responsible.
Show this thread -
Overhauling JavaScript's async surface (promises in ES2015 -> async function -> async iteration) is a huge project. Adding shared memory and atomics to a run-to-completion language is a huge project.
Show this thread -
The next big cross-cutting feature set (class improvements) has *also* been a big project, and many of the features have made it to Stage 3 and implementation work (which is more than you can say about ES6 when it was "shipped").
Show this thread -
I think the pace of change is actually pretty fast, and speaking only for myself, I think moving more big cross-cutting features through the pipeline even quicker would not be an improvement.
Show this thread
End of conversation
New conversation -
-
-
If things ship before standardization, won’t you have people building on top of wip features and then crying foul if they change in the standard? Wouldn’t it be better for them to be implemented but only available in beta builds (vs. “shipped” to everybody)?
-
Stage 3 is "we're pretty sure we're done, modulo any urgent concerns that come up during implementation". The impls happen behind a flag, and get unflagged once engines are ready to advance to stage 4 (and freeze).
-
There's a bit of a dance at the final stretch that we're still getting used to, but in broad strokes it works.
End of conversation
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.