Logistics
Facilitator(s)
@nicolo-ribaudo (Igalia), but happy to have somebody else do it instead
Summary
The way the web integration of proposals in TC39 is done varies a lot by proposal, and it depends a lot on how the proposal's champion decides to approach it. Some examples:
- AsyncContext went with an "all-in" approach, trying to deeply integrate the proposal in as many web APIs as possible
- Temporal went with a minimal approach, basically only adding it to structuredClone, even if there is a potential of a good integration with timer-like APIs or HTML inputs
- Explicit resources management has no web integration, even though it's a proposal especially useful for I/O resources and the web platform defines many of those
Proposals also have different needs, some of those are only useful with a proper web integration (such as import attributes), and for some it's completely useless (for example, the various Atomics-related features).
For some proposals, TC39 started working on a model where having a clear idea of what the web integration will look like is a Stage 2.7 blocker, but it's not applied consistently.
How can we work together better, to smooth the process and make sure that good potential DX improvements don't get forgotten just because of missing communication?
Let's go through proposals that are stage 2/3/4 and think about what is the best web integration we can aspire to, rather than the minimum to make it work.
Type
Onsite
Other comments
Logistics
Facilitator(s)
@nicolo-ribaudo (Igalia), but happy to have somebody else do it instead
Summary
The way the web integration of proposals in TC39 is done varies a lot by proposal, and it depends a lot on how the proposal's champion decides to approach it. Some examples:
Proposals also have different needs, some of those are only useful with a proper web integration (such as import attributes), and for some it's completely useless (for example, the various Atomics-related features).
For some proposals, TC39 started working on a model where having a clear idea of what the web integration will look like is a Stage 2.7 blocker, but it's not applied consistently.
How can we work together better, to smooth the process and make sure that good potential DX improvements don't get forgotten just because of missing communication?Let's go through proposals that are stage 2/3/4 and think about what is the best web integration we can aspire to, rather than the minimum to make it work.
Type
Onsite
Other comments