A year long feature freeze for JS where no new features and proposals are released would be:
-
stage 0 things being “pushed” doesn’t mean much. Object.observe was stage 2 and got dropped.
yeah but then there's cancellation tokens, new wave promise error handling and what not. It's a lot; and a break might be good
-
-
like: node 0.10 was when things flourished; stability for a while is good (as long as we're not unable to move forward after that)
-
a loss of momentum would constitute exactly that. ES6 took five years and that’s just too long.
- 3 more replies
New conversation -
-
-
you can just ignore cancellation if you want to; the committee will make sure existing code never breaks.
-
Oh it's not code breakage I'm worried about, it's the flood of additions. Are they a good idea? Nobody knows; dust hasn't settled
- 3 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.