20 comments

[ 2.8 ms ] story [ 30.2 ms ] thread
I guess we can come full circle and eventualy port it to Android Java.
Is this being handed over to the Bytecode Alliance or is this a hard fork and will diverge from Chicory? It isn't clear from the announcement but I suspect the former.
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
Finally we can run Kotlin/WASM on desktop! /s
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/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.

if i understand correctly, the new redline compiler doesn't have these limitations. it's not based on asm. (edit: but this hasn't been merged to mainline yet)
Another Shameless plug: A common interface for webassembly engines, including Chicory, in Java https://github.com/tegmentum/webassembly4j
I wrote this for a number of reasons but oddly enough Java probably has the most options as far as runtimes go but the support is pretty fractured. The underlying runtime adapters add support for wasmtime and wamr as well. There are two JNI implementations for wasmtime but they are badly out of date and haven't been updated in years. There are a number of reasons you might want to use one runtime over another and this was supposed to unify them under a single interface and make swapping them out easy. It also allows you to easily compare the tradeoffs of various engines.
Why not resurrect applets? We had this webasm thing 30 years ago.
I was trying to write something like this in rust at some point, just for the joke that you can compile that rust to wasm, and then it can compile itself to JVM assembly. The complexity of it turned out to be quite a bit too high for a joke only.