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 haven't been around enough to have a strong sense, but maybe there's a need for some periods where the language moves in big ways, and other periods where change is more incremental. Big steps, then consolidation.
-
I think we also need a stronger sense that a feature might be good in isolation, but nonetheless not gonna make it right now. Increasingly, it feels like a very serious personal affront to object to an early stage feature.
-
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
- 7 more replies
New conversation -
-
-
Maybe a group of the champions of class features, pipeline, null coalescing (I think those are the main cross cutting features) can get together to propose some changes to how proposals with that much cross-cuttingness go through the process?
-
I definitely like the idea of champions getting together and working out these issues, but I don't know if it needs to be all at once. From a technical perspective, I don't think there's much "cross-cutting-ness" between class features and the expression-related features.
-
The cross-cutting concern is the very nature of the language. What is JavaScript? What characterizes it as a unique language? What fits in and what does not?
-
There are some things we can discuss in plenary, about the whole language, and then there are more fine details that we can work out in groups that are focused on details on a group of closely related features.
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.