Re:Missing the Point of WebAssembly
by davexunit on Tuesday January 09, 2024 @03:12PM
(#38931397)
The type system introduced in Wasm GC allows sharing data between the host and other modules and is usable right now. DOM access is possible and being demonstrated in several language implementations.
[ Parent
| on HN ]
Re:Missing the Point of WebAssembly
by schemescape on Tuesday January 09, 2024 @04:30PM
(#38932377)
I saw you mention this in a previous post, but I can’t find an example. Do you have one handy? What are the limitations?
Edit: is this it? https://www.spritely.institute/news/building-interactive-web...
Edit again: apparently I had seen this before, since I upvoted its HN submission. Oops! https://news.ycombinator.com/item?id=38477602
Yup, that's one of the examples! And here's another: https://spritely.institute/news/scheme-in-scheme-on-wasm-in-...
Re:Missing the Point of WebAssembly
by singularity2001 on Tuesday January 09, 2024 @03:17PM
(#38931475)
are you sure? the last time I checked JavaScript was NOT able to access Wasm/GC objects
Re:Missing the Point of WebAssembly
by paroneayea on Tuesday January 09, 2024 @03:35PM
(#38931730)
Yes, we have made use of JS invoking WASM-GC managed Scheme objects in our Hoot demos at Spritely.
Re:Missing the Point of WebAssembly
by singularity2001 on Tuesday January 09, 2024 @03:44PM
(#38931840)
In Chrome 120 I still get:
TypeError: WebAssembly objects are opaque
When trying to read/write WASM-GC objects in JS.
Wasm modules have been able traffic in (opaque) host references since the reference-types proposal landed several years back.