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.
1 reply 0 retweets 1 like -
This conversation is weirdly abstract. Can someone talk about which recent language changes are causing concern and why?
2 replies 0 retweets 3 likes -
I think
@awbjs has a problem with decorators, but I don't want to speak on his behalf.1 reply 0 retweets 0 likes -
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
1 reply 0 retweets 1 like -
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.
1 reply 0 retweets 1 like -
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.
1 reply 0 retweets 2 likes -
Replying to @littledan @wycats and
For new proposals, I'm happy to see that many come with early implementations in transpilers and polyfills. I think we can spend time getting more feedback from the JS developer community on these to make sure we are not making a mistake.
1 reply 0 retweets 1 like -
Replying to @littledan @wycats and
But, I don't want to talk about this as if it were a simple budget--understanding a language is more complicated than that, and it's just not actionable feedback for those who want to look into changes. We can direct contributors' energy into careful study.
2 replies 0 retweets 1 like -
Replying to @littledan @polotek and
Totally agree. When pieces fit together nicely, they cost drastically less per feature than if they chafe against each other. Decorators and public/private fields took their time (and then some) and I think it's ok if other new features take time to get feedback and get refined.
1 reply 0 retweets 1 like
The transpiler feedback loop is pretty strong, and letting people play with a collection of features to see how they'll be used in practice feels like a good way to understand what we're doing and take our time with it.
-
-
There's a lot to work through for transpilers, like how do we make sure they don't become unmaintainable, and how do we manage expectations about stability (it will be unstable). But I think it will pay for itself if we can get enough help from the community.
0 replies 1 retweet 1 likeThanks. 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.