Wazero: The zero dependency WebAssembly runtime for Go developers

I happen to work on a lot of profiling and debugging tools and I’ve been wondering if the wasm spec has included anything about the “debugability” of wasm binaries. After a quick scan of the table of contents I couldn’t find it but I’d be curious to hear from anyone who might know. I fear that with an explosion of wasm runtimes (this looks super cool but also I think the 4th or 5th wasm runtime I’ve noticed) that debugability will be a nightmare if it’s not in the spec.

Looks like the compiler includes support for amd64 and arm64 code generation. It's unclear if you can compile WASM to assembly at runtime and invoke it? If so, it might be a viable way to implement plugin support.

Could this be used to deploy Go CLI programs as web apps?<p>I haven’t worked with WASM before, but it seems like you should be able to sniff the CLI definition and expose the arguments and flags as basic web components &#x2F; widgets.

Neat! Few questions: whats the compiled size? Any performance numbers? How is it easier to access functions and types from WASM to Go, and vice versa?

This looks pretty awesome, zero deps! I was wondering how I was gonna host other languages in my Go programs, this is a contender.

I’d love to see benchmarks.

How do y&#x27;all feel about Google shuting down your app by simply suing you over patents from the license?

So far Zig, Odin and Go are the best languages for WASM<p>C&#x2F;C++ is a solid choice too thanks to EMSCRIPEN, but it is very slow to compile, and is not very clean solution<p>dotnet is just too big for WASM<p>rust is too complicated slow to program with