| 00:33 | <Michael Ficarra> | any Mozilla delegates want to present https://github.com/tc39/ecma262/pull/2233 as a needs-consensus PR at the upcoming meeting? dminor |
| 17:55 | <leobalter> | Michael Ficarra: I like your stage extension proposal (the new stage before stage 3) and I wonder if you should include a bullet for the new stage: HTML integration to happen before Stage 3. This would meet exactly where ShadowRealms are right now and clear out a lot of bumps we faced. |
| 17:56 | <leobalter> | the bullet would be more specific to the Slide 7: https://docs.google.com/presentation/d/1HtcFY98qWy-LPJLawRIkYzhDEjuEeyArMiNXbCOFcrk/view#slide=id.g252bc9353ee_0_3049 |
| 19:19 | <Michael Ficarra> | leobalter: I think that should probably be pursued as a follow-on. Currently, the only new entrance requirement is the sufficiency of the tests. I would rather get that part settled and then later, once we have the new stage as our foundation to build on, consider additional entrance requirements. I don't want any added complexity to potentially compromise and further delay this change. |
| 19:25 | <leobalter> | I have no blocking takes. I think the idea is valid, it has been raised and technically if a champion wants to go faster to Stage 3 they can get those items ready along with Stage 2. I think the challenge is gonna be around "no flip-flopping". Perhaps the expectation of mitigating them is raised, but I wouldn't be surprised to continue (now less) implementation details coming up to change a few things. |
| 19:38 | <Michael Ficarra> |
I don't know what this means |
| 21:58 | <shu> | iterator helpers has a web compat issue and chrome is unshipping for now: https://github.com/tc39/proposal-iterator-helpers/issues/286 |
| 22:01 | <bakkot> | noooooooooooo |
| 22:05 | <shu> | the athletic is too big to not unship :( |
| 22:06 | <Kris Kowal> | I read that more as Vader meme than imperative, but yes. |
| 22:07 | <Kris Kowal> | Our sympathies, @bakkot. Here we go again. |
| 22:09 | <shu> | does anyone have a web dev contact at NYT? |
| 22:09 | <shu> | i'm asking internally as well more couldn't hurt |
| 22:15 | <Luca Casonato> | shu: is there data on if this impacts many other sites outside of the athletic? |
| 22:15 | <shu> | no additional data on my end, no |
| 22:16 | <shu> | i also don't know how we would get data outside of one-off reports of "this site doesn't work" like this one |
| 22:16 | <shu> | my hunch is that there's a lot of old regenerator runtime out there, but very unlikely that those sites also freeze Iterator.prototype |
| 22:17 | <shu> | unless this airgap.js thing is industry standard for doing whatever it does, then we have a problem |
| 22:17 | <shu> | since it looks like a paid product |
| 22:17 | <Kris Kowal> | The two-year-old fix for regenerator runtime was motivated by users of SES. |
| 22:18 | <shu> | i could tell! |
| 22:21 | <Kris Kowal> | I’d say “run npm outdated more”, but I also have reason to assume Uber’s still running Node.js 0.10.36 in prod today and despair. |
| 22:26 | <bakkot> | theathetic is loading airgap.js from transcend's CDN - maybe we can get transcend to update their thing? though not totally clear what change would fix this |
| 22:27 | <Kris Kowal> | Regenerator Runtime gets injected by bundlers (I think Rollup) if the target language is set down toward es5. |
| 22:28 | <nicolo-ribaudo> | It's injected by Babel when compiling generators, but the version that's injected depends on what the user has in their package.json |
| 22:28 | <Kris Kowal> | So it’s safe to assume this can be fixed by a configuration change in the deployment of theathletic. |
| 22:29 | <bakkot> | what if we just delete Iterator.prototype.constructor |
| 22:37 | <shu> | what if we just |
| 22:37 | <shu> | the former seems unlikely because NYT is a big property and have staff |
| 22:39 | <shu> | theathetic is loading airgap.js from transcend's CDN - maybe we can get transcend to update their thing? though not totally clear what change would fix this |
| 22:39 | <shu> | which sgtm, i don't know why they do this anyway |
| 22:39 | <bakkot> | what if we get airgap to delete Iterator.prototype.constructor before freezing anything |
| 22:40 | <shu> | ah, sure, that's a possible fix |
| 22:40 | <bakkot> | or they could replace it with a getter/setter pair if they want to preserve behavior |
| 22:40 | <shu> | 117 goes stable in 3 business days, however, so i'm still unshipping |
| 22:41 | <shu> | if we can get Transcend to workaround perhaps we can fast-track shipping this later? idk, but i'm doing the conservative thing for now |
| 22:53 | <Mathieu Hofman> | We should just fix the override mistake ... |
| 22:58 | <bakkot> | I have gone ahead and @'d the CEO and CTO of transcend on the github thread |
| 23:07 | <Michael Ficarra> | bakkot: from https://github.com/transcend-io/airgap.js-types/commits/main, it appears that @anotherminh is active in the last few hours, consistently active on weekdays, and does work related to airgap-js |
| 23:07 | <Michael Ficarra> | you should give them a mention as well |
| 23:09 | <bakkot> | done |
| 23:09 | <bakkot> | assuming editing in someone's handle pings them, anyway |
| 23:09 | <Michael Ficarra> | I think it does |
| 23:19 | <Mathieu Hofman> | I don't think editing does ping |
| 23:23 | <Mathieu Hofman> | oh maybe it does these days: https://github.com/isaacs/github/issues/310 |
| 23:47 | <shu> | oh hey someone from Transcend replied! if they transparently roll this out before i can get the unshipping merged for 117, then i'll let it stay shipped for 117 |