11–20 of 44 posts
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.
And discussed the roadmap.
Blogpost and video here: https://blog.cosmonic.com/engineering/2026-05-26-diving-into...
What got me into this is I just finished a major release of Petrify (https://github.com/exabrial/petrify) that compiles ML Models to JVM Bytecode. It requires Jdk25 to do the compilation, but the compiled models can run on Jdk17+.
I'm looking for more side projects to use the classfile API on.
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.
The component model is still in phase 1 (standardization is phase 5) and the Bytecode Alliance are its sponsors and the ones pushing it into the ecosystem with wasmtime.
The point of a component model is interoperability, so the more runtimes that support it the better.
Earlier quoted context omitted.
The component model is still in phase 1 (standardization is phase 5) and the Bytecode Alliance are its sponsors and the ones pushing it into the ecosystem with wasmtime.
I don't think you're fully saying what you want to here. Are you saying this is bad? The point of a component model is interoperability, so the more runtimes that support it the better.
Lots of context for this project on the Bytecode Alliance blog: https://bytecodealliance.org/articles/endive-and-the-next-ch...
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…
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
> 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?