May 28, 2026
Fork around and find out
Endive: A JVM native WebAssembly runtime
Java gets its own Wasm engine, and the comments are already asking who really owns it
TLDR: Endive is a new Java-friendly way to run WebAssembly without extra native software, aiming to make deployment simpler and safer. Commenters were intrigued but immediately split between hype, rival-tool name-dropping, and confusion over whether this is a smooth handoff or the start of a messy fork story.
A new project called Endive just showed up with a big promise: run WebAssembly programs inside Java without extra native add-ons, which is basically catnip for anyone tired of shipping a pile of platform-specific files. The pitch is simple enough for non-experts: if your app already runs wherever Java runs, Endive wants WebAssembly to tag along without breaking that convenience. It also arrives with serious pedigree, now hosted by the Bytecode Alliance, and carrying over years of work from its earlier life as Chicory.
But the real action? The comments immediately turned into a mini soap opera about what this thing actually is. Is Endive a clean handoff into the Bytecode Alliance family, or a full-on fork drama that could split from Chicory? One commenter bluntly said the announcement wasn’t clear and started reading the tea leaves. Another instantly dropped a rival receipt in the chat by linking GraalVM’s WebAssembly docs, basically saying: “Cute, but this isn’t the only game in town.”
Then came the classic internet mood swing from serious to absurd. One person joked that maybe we’ve gone so far around the circle we’ll end up porting it to Android Java, while another tossed in a talk titled “The Birth & Death of JavaScript” like they were trying to start a side quest in the middle of the thread. The vibe is equal parts excitement, skepticism, and nerdy popcorn energy: people like the “no native dependencies” promise, but they also want to know who’s steering the ship before they fully clap.
Key Points
- •Endive is a Bytecode Alliance-hosted, JVM-native WebAssembly runtime that runs without native dependencies or JNI.
- •The project is a fork of Chicory, and the article credits Dylibso, Inc. for the incubation and foundational work.
- •The article argues that native Wasm runtimes create distribution and runtime integration challenges for Java applications because they require platform-specific native binaries and FFI.
- •Endive’s stated goals include safety, support for restrictive JVM environments, full support for the core Wasm spec, and idiomatic integration with Java and other host languages.
- •The roadmap lists many completed capabilities, including a parser, interpreter, validation, v1.0 API, compiler support, WASIp1, SIMD, tail calls, exception handling, threads, GC support, and multi-memory support, with performance and WASIp2 still ongoing.