Re: [go-nuts] Is WASM support planned in go 1.12 ?

Ill be following your repo closely Max. Really like the looks of it! On Thursday, February 21, 2019 at 3:40:47 PM UTC-6, max...@segment.com wrote: > > I'm working on a wasm go library to build front end. > It is unstable on mobile but work fine on desktop (except Edge). > Waiting for go 1.12 to

Re: [go-nuts] Is WASM support planned in go 1.12 ?

I'm working on a wasm go library to build front end. It is unstable on mobile but work fine on desktop (except Edge). Waiting for go 1.12 to solves some issues. If you are on a desktop, you see the hello world example built with it here: wasm go hello world T

Re: [go-nuts] Is WASM support planned in go 1.12 ?

To add to what Keith has said, Callback has been renamed to Func because the function will get called synchronously instead of being async. This is one of the major changes in 1.12. On Thursday, 7 February 2019 05:11:50 UTC+5:30, Keith Randall wrote: > > To answer the OP, wasm support is in 1.1

Re: [go-nuts] Is WASM support planned in go 1.12 ?

On Wed, 6 Feb 2019 12:30:51 -0800 Tharaneedharan Vilwanathan wrote: > Somehow I was dreaming I can use Go for frontend too, instead of JS. Is my > thinking right? It is wrong, in my opinion. Just use a right tool for a task. If you do want go-like experience for browser frontend I'd suggest usi

Re: [go-nuts] Is WASM support planned in go 1.12 ?

No need to learn JS if you learn Typescript. Straight JS is pretty dead except for older codebases or trivial applications. > On Feb 6, 2019, at 5:54 PM, Manlio Perillo wrote: > > On Wednesday, February 6, 2019 at 9:07:16 PM UTC+1, Tharaneedharan > Vilwanathan wrote: > > I have one more quest

Re: [go-nuts] Is WASM support planned in go 1.12 ?

On Wednesday, February 6, 2019 at 9:07:16 PM UTC+1, Tharaneedharan Vilwanathan 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 i

Re: [go-nuts] Is WASM support planned in go 1.12 ?

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

Re: [go-nuts] Is WASM support planned in go 1.12 ?

Thanks, Russtopia and Ian! On Wed, Feb 6, 2019 at 1:07 PM Ian Denhardt 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:

Re: [go-nuts] Is WASM support planned in go 1.12 ?

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 perfo

Re: [go-nuts] Is WASM support planned in go 1.12 ?

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.

Re: [go-nuts] Is WASM support planned in go 1.12 ?

I have used gopherjs for some small projects; it's pretty nice and lets you 'think in Go' yet still access the DOM pretty easily. I am no JS expert, so using it let me sidestep some of the ugliness there. It definitely made doing async stuff nicer, using goroutines instead of lots of callback-style

Re: [go-nuts] Is WASM support planned in go 1.12 ?

Somehow I was dreaming I can use Go for frontend too, instead of JS. Is my thinking right? Regards dharani On Wed, Feb 6, 2019 at 12:26 PM Robert Engels wrote: > Just mo wasm is horrible on any platform. Unless you maybe have a > large game engine that you are attempting to integrate. > >

Re: [go-nuts] Is WASM support planned in go 1.12 ?

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 in

Re: [go-nuts] Is WASM support planned in go 1.12 ?

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 O

[go-nuts] Is WASM support planned in go 1.12 ?

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