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

WASM #17

Open
flying-sheep opened this issue Jul 8, 2018 · 0 comments
Open

WASM #17

flying-sheep opened this issue Jul 8, 2018 · 0 comments

Comments

@flying-sheep
Copy link

flying-sheep commented Jul 8, 2018

First of all: I think it’s useless to distinguish bytecode and text representations of WASM. They correspond 1:1, that’s tr, not a compiler.

Generally I think everything will compile to WASM at some point very soon in the future. Right now:

  • JWebAssembly compiles Java bytecode to WASM
  • Using LLVM:
    • EMScripten compiles C/C++ to JS or WASM
    • Rust has WASM as direct compiler target

I think rust is the most mature and convenient bet right now, you can compile your library directly to a WASM library by setting the compile target mode and import the resulting file from a JS runtime.

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

1 participant