What does HackerNews think of wasm-micro-runtime?

WebAssembly Micro Runtime (WAMR)

Language: C

#6 in Java
#5 in JavaScript
#6 in PHP
I would if anything worked.

Still waiting for a Windows release of this: https://github.com/bytecodealliance/wasm-micro-runtime

Don't hold you breath.

Also needs Risc-V and ARM 32/64.

I'm considering building a Java compatible VM that only has static memory allocation to avoid GC.

Why hasn't this been done by anyone yet?

Also confused why this does not have a binary windows release yet: https://github.com/bytecodealliance/wasm-micro-runtime

Edit: Epsilon is not the answer here you can stop mentioning that.

Seems the micro runtime also released 1.0:

https://github.com/bytecodealliance/wasm-micro-runtime

But why does it not have binaries compiled and ready?

nm: https://github.com/bytecodealliance/wasm-micro-runtime/issue...

What's the difference behind this and https://github.com/bytecodealliance/wasm-micro-runtime?

I'm using wasm-micro-runtime at https://www.inngest.com to transform events on the fly, to run secure templating everywhere, and (sometimes) to run custom actions.

WAMR also has the capability to run AOT compiled WASM, which is kind of ideal for the immutable, fast running wasm modules we're running.

Would love to learn more, because it seems like they have shared goals, and this is a very, very interesting subject :)

I've recently been working on WASM VM embedding with C (well, via libffi) for a personal project and uncovered a couple of WASM VM options, wasmtime & wasmer:

* https://github.com/bytecodealliance/wasmtime

* https://wasmerio.github.io/wasmer/c/runtime-c-api/

The underlying implementation of each is written in Rust.

(Recently I also discovered there's a "micro VM" too: https://github.com/bytecodealliance/wasm-micro-runtime)

The official WASM C API is still WIP but wasmtime targets it directly: https://github.com/WebAssembly/wasm-c-api/

Not sure if Wasmer is aiming for compatibility with the official WASM C API currently.

From my experience, Wasmtime's C support is probably best described as "under-documented but functioning".

I haven't implemented anything with Wasmer.

My impression is that Wasmer may offer a higher level API than Wasmtime but not sure if it counts as "drop in" yet.

Part of the reason why I ended up going with Wasmtime was...I kinda forgot Wasmer existed. :D But also I do like that they're targeting what will hopefully become a standard API--but I think that results in a lower level API than what is most "friendly" for starting out.

Been meaning to make this embedded Wasmtime C API example--created while figuring things out--public after tidying it up a bit more but... well, I just now made it public, as is (it at least has a ReadMe now :D ): https://gitlab.com/RancidBacon/wasm-embed-test :)

Also, this is one option for test compiling C to WASM without setting up a tool chain: https://wasdk.github.io/WasmFiddle/

Some of my notes from development so far: http://www.labradoc.com/i/follower/p/notes-webassembly#20200...

Edit: Grammar. Add & then move micro WASM VM link.

Where did you get ~1million number? https://github.com/bytecodealliance/wasm-micro-runtime is less than 100K LoC for example.