The State of WebAssembly 2022

Re:The State of WebAssembly 2022 by tormeh on Monday June 20, 2022 @02:13PM (#31813629)

I wish I could somehow ship a website as a single wasm file. Currently there's quite a bit of HTML/JS ceremony involved in order to execute a wasm file, but I'd rather be able to serve up an "index.wasm" and be done with it. Is there any movement towards this?

[ Parent | on HN ]

Re:The State of WebAssembly 2022 by sitkack on Monday June 20, 2022 @03:37PM (#31814713)

The ceremony is a one time thing, and the boilerplate is a copy and paste away. You can pretty easily ship an entire application as an self contained html file.

[ Parent | on HN ]

Re:The State of WebAssembly 2022 by trusktr on Wednesday June 29, 2022 @10:59AM (#31921105)

I was thinking to fork a browser engine, and bind wasm directly to the DOM without any JS. Anyone interested in teaming up on this?

[ Parent | on HN ]

Re:The State of WebAssembly 2022 by singularity2001 on Monday June 20, 2022 @03:05PM (#31814281)

yes, <src module="main.wasm"/> is under consideration. Maybe you need a tiny wasm_dom.js but direct DOM manipulation is in the pipeline too.

[ Parent | on HN ]

Re:The State of WebAssembly 2022 by postalrat on Tuesday June 21, 2022 @10:07AM (#31824120)

Where is the spec for either of those? The <src> doesn't even make sense.

[ Parent | on HN ]