Skip to content
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

How this crate positions itself against stdweb? #37

Closed
rylev opened this issue Feb 22, 2018 · 1 comment
Closed

How this crate positions itself against stdweb? #37

rylev opened this issue Feb 22, 2018 · 1 comment

Comments

@rylev
Copy link
Contributor

rylev commented Feb 22, 2018

It seems that stdweb aims to do a lot of the same things wasm-bindgen does (and some more). How is this crate positioned against stdweb? Is it a strict competitor (i.e. more choice, the better) or does it aim to be something different?

@alexcrichton
Copy link
Contributor

I think that they're both targeted at making interop with JS through wasm to be nicer, although from my understanding they're taking different approaches and are intended for different use cases. With wasm-bindgen in particular the vision at least is to be a tool that any language can use, not just Rust. Ideally C++/other wasm languages would converge on a similar standard so there's only one wasm-bindgen tool and each language compiles down to the tool's intended interface.

In any case I think for now it's great to have multiple options, and we can see where wasm goes!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants