Just mo.... wasm is horrible on any platform. Unless you maybe have a large game engine that you are attempting to integrate.
You have to ask yourself, what are you trying to do? If it is just to avoid the garbage that is JS, then use an environment that transpiles to JS. You’ll have better integration with the DOM, and not have to learn yet another client side technology. Again, just mo. > On Feb 6, 2019, at 2:06 PM, Tharaneedharan Vilwanathan <vdhar...@gmail.com> > wrote: > > > I have one more question. Has anyone used WASM in Go for something more than > small examples I managed to see and got them working? > > It was challenging to get it working and then I wasn't sure how it is used > and how to use it for any bigger projects. > > Please share your thoughts. > > Regards > dharani > > >> On Wed, Feb 6, 2019 at 11:57 AM gocss <g...@curtissystemssoftware.com> wrote: >> while webassembly was considered experimental in go 1.11 is it >> planned in go 1.12 release later this month? If so will it's inclusion be >> considered non-experimental ? >> -- >> 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. -- 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.
