To answer the OP, wasm support is in 1.12 and is still experimental. There have been some changes to the wasm support but nothing major. (See the syscall/js section of https://tip.golang.org/doc/go1.12 for details.)
On Wednesday, February 6, 2019 at 2:27:53 PM UTC-8, Tharaneedharan Vilwanathan wrote: > > Thanks, Russtopia and Ian! > > On Wed, Feb 6, 2019 at 1:07 PM Ian Denhardt <i...@zenhack.net > <javascript:>> wrote: > >> Quoting Tharaneedharan Vilwanathan (2019-02-06 15:30:51) >> >> > Somehow I was dreaming I can use Go for frontend too, instead of JS. >> Is >> > my thinking right? >> >> If that's your interest use gopherjs instead: >> >> https://github.com/gopherjs/gopherjs >> >> It's been around a long time and is pretty mature. >> >> As others have said, talking to the DOM in wasm is clumsy at best (and >> there's nothing Go-specific about this). If you want to make significant >> use of browser APIs, Javascript is a better target. >> >> -Ian >> > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
