News for hackers. Stuff that matters.
Re:Dynamic Translation of Smalltalk to WebAssembly by dgb23 on Tuesday July 09, 2024 @10:01AM (#40916267)
There seems to be alot of work going into WASM itself, much of it is performance related:

https://github.com/WebAssembly/proposals

Re:Dynamic Translation of Smalltalk to WebAssembly by mjhay on Tuesday July 09, 2024 @10:48AM (#40916774)
If only you could directly access the DOM or other browser APIs. I understand the GC proposal might help with this (?).
Re:Dynamic Translation of Smalltalk to WebAssembly by dgb23 on Tuesday July 09, 2024 @02:52PM (#40919521)
I found a discussion with some explanations to why that is and what other solutions could be looked at:

https://github.com/WebAssembly/design/issues/1184

Re:Dynamic Translation of Smalltalk to WebAssembly by mjhay on Tuesday July 09, 2024 @04:50PM (#40920937)
Thank you. That helps with my confusion a lot.
Re:Dynamic Translation of Smalltalk to WebAssembly by andsoitis on Tuesday July 09, 2024 @10:24PM (#40923206)
”The main reason is that direct access to the DOM requires the ability to pass references to DOM/JS objects through Wasm. Consequently, when GC happens for JavaScript, the collector must be able to find and update such references on the live Wasm stack, in Wasm globals, or in other places controlled by the Wasm engine. Hence the engine effectively needs to support GC in some form.

However, the new proposal for reference types that we split off from the GC proposal tries to give a more nuanced answer to that. It introduces reference types without any functionality for allocating anything within Wasm itself. In an embedding where host references are garbage-collected that still requires a Wasm implementation to understand GC. But in other embeddings it does not need to.”

Re:Dynamic Translation of Smalltalk to WebAssembly by mason_mpls on Tuesday July 09, 2024 @10:23PM (#40923196)
As someone who wants WASM to free us all from JS. Is this even worth it if DOM bindings for WASM will never get a released? I’ve been following this since 2018 and it seems like we’re still at square 1 with DOM bindings. Incredibly frustrating.