3 ms·

I was under the impression that direct interaction with the DOM from WASM was predicated on GC support. Does this mean that something like python could now dire

I was under the impression that direct interaction with the DOM from WASM was predicated on GC support. Does this mean that something like python could now directly access the DOM without javascript?

Skinney 3y ago
I don't think WASM has API's for accessing the DOM, so you'll still need a little bit of glue code. The GC support allows you to safely pass GC objects around without them dissapearing (being collected) on you.
- singularity2001 3y ago
  "a little bit" of glue code
flohofwoe 3y ago
AFAIK GC is (mostly) irrelevant for "direct DOM access", you would rather want to hop into the following rabbit hole: - reference types: https://github.com/WebAssembly/reference-types/blob/master/proposals/reference-types/Overview.md https://github.com/WebAssembly/reference-types/blob/master/p... - interface types (inactive): https://github.com/WebAssembly/interface-types/blob/main/proposals/interface-types/Explainer.md https://github.com/WebAssembly/interface-types/blob/main/pro... - component model: https://github.com/WebAssembly/component-model https://github.com/WebAssembly/component-model If this looks like a hot mess, that's because it is. Compared to that, the current solution to go through a Javascript shim doesn't look too bad IMHO.
- johncolanduoni 3y ago
  Yeah I think the component model is biting off way too much in one proposal. All the future WASI developments are gated on it too now so we won’t see any improvements there either until this all-singing, all-dancing universal interop is shipped.
WorldMaker 3y ago
It's definitely a big step in the direction towards direct DOM interaction, but not yet the full path.