Live data from Hacker News

Endive: A JVM native WebAssembly runtime

github.com

41–44 of 44 posts

Re: Endive: A JVM native WebAssembly runtime

#41
post #19

Projects like this would be significantly funner and easier to make in Jdk25+(well technically 24+) because of the new Java classfile/bytecode API. It looks like Endive uses OW2 ASM, probably because this supports back to Jdk11. The new jdk API has a minimum target of Jdk17. OW2 ASM is significantly harder to use IMHO though. What got me into this is I just finished a major release of Petrify ( https://github.com/exa…

You might want to take a look at https://www.graalvm.org/webassembly . Runs on JDK25 and has very good guest host interop.

There is a comparison between the two here:

https://www.linkedin.com/feed/update/urn:li:activity:7465778...

Re: Endive: A JVM native WebAssembly runtime

#43

This is a fork of Chicory, a bit more context of the relationship between the projects can be found here: https://github.com/dylibso/chicory/issues/1296

Any background / context around what the Chicory author means in this comment? > We'll consider merging in changes that make sense from Endive, but under the stewardship of the [Byte Code Alliance] I have very little faith in its future. My words mean nothing though having all but completely lost interest and use for WebAssembly. What's the background / history of Byte Code Alliance?

The comment is from the Dylibso CEO.

Re: Endive: A JVM native WebAssembly runtime

#44

It will be really great if this becomes a second popular runtime with both GC and WASI component model support. Wasmtime being the only runtime with that combo is a bit concerning. Node supporting the component model will help a lot too.

Component model can run in any js runtime with jco
Post reply on HN