A year long feature freeze for JS where no new features and proposals are released would be:
-
-
-
Replying to @ljharb
take a break and reflect on things. There's a lot of issues right now and having breathing room might be what we as a community need
1 reply 0 retweets 2 likes -
-
Replying to @ljharb
social, technical. People burning out, stuff like zones being pushed. Idk, maybe we need a break to chill and reflect for a bit
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
stage 0 things being “pushed” doesn’t mean much. Object.observe was stage 2 and got dropped.
1 reply 0 retweets 0 likes -
Replying to @ljharb
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
2 replies 0 retweets 1 like -
Replying to @yoshuawuyts
you can just ignore cancellation if you want to; the committee will make sure existing code never breaks.
1 reply 0 retweets 0 likes -
Replying to @ljharb
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
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
perhaps you’re not aware that most of these “new additions” have been baking for years already?
1 reply 0 retweets 0 likes
oh, I know - but as an end user of the language the process itself is less interesting to me than the problems we deal with using it
-
-
Replying to @yoshuawuyts
then how would altering the timing of the process affect you in any way?
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.