| 00:41 | <Kris Kowal> | I sketched guybedford (Guy Bedford) and Luca Casonato ’s ModuleInstance in the context of the Loader née Compartments proposal https://github.com/tc39/proposal-compartments/pull/51 |
| 00:42 | <Kris Kowal> | In short, it doesn’t obviate the need for Loader, because dynamic import has to fall through. |
| 00:42 | <Kris Kowal> | It may be interesting to include a ModuleInstance constructor regardless, but it doesn’t reduce the scope of the Loader proposal. |
| 01:23 | <Kris Kowal> | On further reflection (updated above PR, it’s possible to implement Loader in user code, with all of the “static import” part of Import Reflection, ModuleInstance, and a Global constructor for the hardened JavaScript case. The user-code Loader wouldn’t be able to do import reflection on your behalf, so you’d have to learn harder on that. |
| 01:24 | <Kris Kowal> | The user code loader would have to thread a dynamic import (or not). |
| 03:50 | <Kris Kowal> | guybedford: When you say “Synthetic”, as in static module record, is that equivalent to how I’ve been using “third-party” in the Loader (née Compartments) proposal? If so, I like it and would be glad to propose a change. |
| 04:46 | <Kris Kowal> | Oh, story checks out. You’re borrowing a term from WebIDL https://github.com/tc39/proposal-compartments/issues/36 |
| 05:52 | <Jack Works> | can I join the zoom meeting with a web client and be able to share screen? 👀 |
| 05:53 | <Jack Works> | for this event |
| 06:52 | <naugtur> | you definitely can join, didn't test sharing |
| 06:53 | <naugtur> | we can switch to something else if that's an issue |