Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
For those that don't know. Wasm is a bytecode that aims to improve performance in browsers. Instead of having to interpret quite complex high-level code, the wasm interpreter takes a specialized bytecode and runs that on a simulated cpu. This not only promises to be a lot more performant than JS but it gives us another big advantage: In theory any language can be compiled into. The biggest supported languages atm are C++, Rust, JS, Ruby, Go and Python. Kotlin and Java are not officially supported, but Kotlin supports native compilation to WASM and Java has the JWebAssembly project.
The biggest integration library is wasmer. It's intended as a server runtime for wasm. The official port wasmer-java has the problem of not supporting imports and that's also not to be implemented in the near future (they are restructuring the wasmer library according to this issue), the other is wasmer-jni. An inofficial jni-binding for the wasmer base implementation. Less nice to use, but feature complete.
The biggest integration library is wasmer. It's intended as a server runtime for wasm. The official port wasmer-java has the problem of not supporting imports and that's also not to be implemented in the near future (they are restructuring the wasmer library according to this issue), the other is wasmer-jni. An inofficial jni-binding for the wasmer base implementation. Less nice to use, but feature complete.
Related posts
- Brainfk-rs: A brainfuck to WebAssembly compiler written in Rust
- Brainfk-rs: A brainfuck to WebAssembly compiler written in Rust
- Brainfk-rs: A brainfuck to WebAssembly compiler
- Brainfk-rs: A brainfuck to WebAssembly compiler written in Rust
- Do goroutines typically run ontop of operating system threads?