From the agenda for the 104th meeting of Ecma #TC39 (https://github.com/tc39/agendas/blob/main/2024/10.md#agenda-items). Longer or open-ended discussions: JSSugar/JS0: https://docs.google.com/presentation/d/1ylROTu3N6MyHzNzWJXQAc7Bo1O0FHO3lNKfQMfPOA4o/mobilepresent?slide=id.g30432c5cd9c_0_688. Slide 40 onward 👀:
Let's standardize as the ecosystem uses it:
JS0: the language implemented by the engines
JSSugar: features that must be compiled by tools to JS0
@tomayac I’m late to the game here, but to me this essentially sounds like a call to action to apply and embrace the #extensibleWebManifesto in the TC39 process?
That the core functionality should focus on enabling things that otherwise wouldn’t be possible to implement elsewhere while high level functions can be kept out of the core?
So JS remains JS and JSSugar is simply a standardization of syntax sugars, not of any polyfills, right?
Wrote more here: https://mastodon.social/@voxpelli/113339222276926945
Thomas Steiner 
Pelle Wessman