New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebAssembly support #211

Open
slimsag opened this Issue Sep 6, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@slimsag
Member

slimsag commented Sep 6, 2018

This is probably very easy/straightforward to add. We can keep GopherJS support using build tags.

@slimsag slimsag added the enhancement label Sep 6, 2018

@gedw99

This comment has been minimized.

Show comment
Hide comment
@gedw99

gedw99 Sep 6, 2018

Pretty smarty approach too.

Can even use both together for best performance.
Wasm in the web workers.
Gopherjs in the main Window.

gedw99 commented Sep 6, 2018

Pretty smarty approach too.

Can even use both together for best performance.
Wasm in the web workers.
Gopherjs in the main Window.

@divan

This comment has been minimized.

Show comment
Hide comment
@divan

divan commented Sep 10, 2018

What about this project -
https://github.com/gowasm/vecty?

@gedw99

This comment has been minimized.

Show comment
Hide comment
@gedw99

gedw99 Oct 5, 2018

he says in his readme ( https://github.com/gowasm/vecty) that its "hopefully temporary", so he probably wants to upstream it to Vecty.
Maybe worth asking him @slimsag

gedw99 commented Oct 5, 2018

he says in his readme ( https://github.com/gowasm/vecty) that its "hopefully temporary", so he probably wants to upstream it to Vecty.
Maybe worth asking him @slimsag

@gedw99

This comment has been minimized.

Show comment
Hide comment
@gedw99

gedw99 Oct 5, 2018

@slimsag @damz
i just saw that there is a PR for this !
#215

gedw99 commented Oct 5, 2018

@slimsag @damz
i just saw that there is a PR for this !
#215

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment