It’s still supported and developed, but it’s not an area where most activity is currently focused. It is very stable, even more so when it was first added, sinc

It’s still supported and developed, but it’s not an area where most activity is currently focused. It is very stable, even more so when it was first added, since bugs are being fixed and regression tests are added. You can see what issues are open and closed at https://github.com/golang/go/issues?q=is%3Aissue+label%3AArch-Wasm https://github.com/golang/go/issues?q=is%3Aissue+label%3AArc.... The Wasm specification is also progressing over time, sometimes unblocking some opportunities in the Go implementation. I’ve been using Go in the frontend in many (most?) of my personal projects since the early days of GopherJS, and by now I’ve compiling most of that frontend code to Wasm. I’m very happy with the experience and results, and my top wishlist item would be improvements to the binary size for faster first-time loads. If you haven’t already seen it, https://golang.org/wiki/WebAssembly https://golang.org/wiki/WebAssembly has lots of good info.