From the Mozilla Hacks blog: Making WebAssembly A First-Class Language on the Web

[yosh@toot.yosh.is]

From the Mozilla Hacks blog: Making WebAssembly A First-Class Language on the Web

Making WebAssembly a first-class language on the Web – Mozilla Hacks - the Web developer blog

This post is an expanded version of a presentation I gave at the recent WebAssembly CG meeting in Munich. WebAssembly has come a long way since its first release in 2017. The 1.0 version of WebAssembly was already a great fit for low-level languages like C and C++, and immediately enabled many new kinds of applications to efficiently target the web.

Mozilla Hacks – the Web developer blog (hacks.mozilla.org)

Firefox is experimenting with native WebAssembly Component support in the browser and giving it access to the DOM! It removes pretty much all of the overhead Wasm on the web has today compared to JS. Making it possible for web apps written entirely in Rust to start outperforming JS.

[yosh@toot.yosh.is]

I've legit wanted this for years. This is exactly the reason why I moved from JS to Rust as my main language in 2018. And it’s also why I've been working on Wasm Components for the few several years.

Because you know what's better than a portable tools used for server workloads? If you can make those same tools work for the web too.

[to@hachyderm.io]

@yosh @peri4n Noob question here : is accessibility properly handled in WebAssembly?

[yosh@toot.yosh.is]

@to @peri4n

What do you mean by that? WebAssembly should have access to everything that JS has, so I think the answer is "yes"

[stiiin@infosec.space]

@yosh I have some loose notes laying around for contributing to the conversation, but if wasm is to be a first-class language, we need a wasm-src directive in CSP. There are some audit standards that require CSP and they would definitely forbid wasm-unsafe-eval. (And in order for wasm-src to fully work, we need an alternative to the instantiateStreaming(fetch()) idiom.)