Hey Vincent,
There isn’t really a “big plan” here, people want a lot of different things out of the language and the standards groups are just there to address them as they come up. The reason you’re seeing a lot more activity today is because the TC39 has changed it’s process so that it can evolve more incrementally.
In terms of what I want for the language, it’s mainly about embracing some of the tools in the ecosystem more. TC39 only recently started having Babel involved and it’s had a pretty immediate effect on their process.
A good example of this happening is when Maggie Pint joined TC39 from Microsoft. She worked on Moment.js previously and now she’s bringing a great new Temporal API to JavaScript which would make the Moment.js library significantly smaller or even unnecessary.
I want to see more of that. I want to see TC39 addressing problems that library and tooling authors are having.
A lot of people complain about us continuing to add new features to JavaScript. It’s fair criticism, but I don’t find the argument “there should be only 1 way to do things” very convincing when we have to be backwards compatible forever.
Have mistakes been made in the process? Sure. Recent example from a Twitter debate: const probably shouldn’t have have been added. But it is what it is, and it’s really not doing that much harm.