I’m beginning to think that the best thing for the future of JavaScript would be for TC39 to go back to a 5-10 year release cycle.
-
-
I personally try to push back against features I think are "good but not good right now" before Stage 2, and then focus on fine-tuning after Stage 2.
-
and not just “right now”. Not every good language features idea is necessarily a good fit to every language.
-
But you can't always tell whether a feature will never be a good fit for a language (many bets on that front have been wrong, such as Shared Array Buffer), so I try to focus on what I know now.
-
This conversation is weirdly abstract. Can someone talk about which recent language changes are causing concern and why?
-
I think
@awbjs has a problem with decorators, but I don't want to speak on his behalf. -
More generally, there's a LOT of features in flight and people are getting pretty (legitimately) concerned about landing them so quickly that we don't have time to react to feedback: - class fields - private fields and methods - pipeline - null coalescing - safe navigation
-
And that's not to mention other pretty meaty features that are pretty new, like Shared Array Buffer, async iterators, rest and spread properties, async function itself.
-
It'd true that you can list the things TC39 has been working on and can be presented in an intimidating way. But I think what we've promoted to late stages fits together well and can be learned piece by piece over time.
- 5 more replies
New conversation -
-
-
Part of that is figuring out how to demonstrate that you care about people and their use cases without taking their feature suggestions.
Thanks. 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.