All in all: Cautiously optimistic about #JS0 / #JSSugar but feeling that:

1. This is nothing new, it’s just a call/reminder to the TC39 to embrace the #extensibleWeb approach to new additions
2. Calling it JS0 rather than JS was really bad and made eg me defensive about it all
3. The focus on transpilation is bad if JSSugar is meant to embrace more than syntax only features

#extensibleWebManifesto

5/5

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

For developers, JS = #JS0 + #JSSugar

agendas/2024/10.md at main · tc39/agendas

TC39 meeting agendas. Contribute to tc39/agendas development by creating an account on GitHub.

GitHub