Yes, WebAssembly would be really nice replacement for gopherjs, especially for game development.
Go already reached realtime garbage collection using native runtime, so theoretically we can make smooth games with 60 FPS. But gopherjs transpiles Go into JavaScript, which adds additional overhead. WebAssembly, on the other hand, is basically a sandbox for low-level bytecode which allows manual memory management. I am personally interested in such feature, because I would like to try Go for creating mobile/web graphics app. Go is perfect candidate for gamedev and other realtime graphics apps, but it's potential isn't leveraged yet. On Wednesday, July 8, 2015 at 4:08:22 AM UTC+3, Ilya Kowalewski wrote: > > Salute nuts, > > I read about WebAssembly (WA) recently and this topic haven't left my head > ever since. Am I right that if we had a Go-to-WA translator when actually > becomes standard, we'd been able to run Go applications on the front-end? > That makes hell lot of sense to me. We could kill JavaScript, once and for > all. Among all the modern languages, Go seems to be a pretty great > candidate for such a JS-killer. > > Go team, are you generally going to look into this topic in the near > future? IIRC, Google loved Go, e.g. for networking stuff, who knows, maybe > you guys would love it for front-end? > > Best regards, > Ilya Kowalewski > -- 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.
