I am also not sure about gopherjs performance if using lots of idiomatic Go (i.e. go routines). It is very difficult to get good performance when the underlying platform expects async callbacks, and Go is “blocking”. There is going to be a lot of stack-unwinding… I am sure somebody has run performance tests somewhere…. :)
> On Feb 6, 2019, at 3:04 PM, Ian Denhardt <i...@zenhack.net> 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. -- 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.
