chicory

Agree about Graal being really good. there are some different use cases for embedding wasm in an application. chicory / endive is not just for embedding another language. the main use case was always secure plugin-systems. but there are other use cases. also it's not controlled by Oracle and works well outside of their ecosystem, which i think some people value. this question came up a few times and were addressed in talks and blog articles: https://github.com/dylibso/chicory#on-the-press

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

Others should consider Chicory, enabling JVM apps to run wasm code (compiled from Rust or many other languages) at high speed, securely in-process. JNI introduces a lot of other challenges and sacrifice in terms of portability, memory and retaining observability and control within the JVM. Chicory even supports AOT compilation to translate wasm bytecode to JVM bytecode for native performance. https://github.com/dylibso/chicory

This is what I miss about the Red Power mod for Minecraft. I wonder if GregTech would see the fun in adding some sort of CPU that wouldn't be the worst emulation stacked inside of hand written 'machine' op functions... Offhand, anyone know of any good (either long stable, or better, well maintained and likely to persist) CPU emulators for Java? Something that does 'web assembly' might fit the task if it's reasonable to transpile a fake binary format into real WASM. The first good search result I got was : https://github.com/dylibso/chicory : better than wasmer-java for this use case since it doesn't depend on native binaries. Relating this back to the topic. It would be interesting to have to, at least copy in someone else's if not, write your own Forth interpreter to help bootstrap computers.

Same tip here. We did this with Chicory: https://github.com/dylibso/chicory I'd follow on that, the earlier you can get this test-suite running the better for the iteration speed and correctness of your project. It took a bit of time to make everything work, but once we did, we very quickly got to the point of running anything. The test-suite is certainly incomplete but gets you 95% there: https://github.com/WebAssembly/testsuite

If you have a Java library, take a look at Chicory: https://github.com/dylibso/chicory It runs on any JVM and has a couple flavors of "ahead-of-time" bytecode compilation.

Chicory has some partial wasip1 support. https://github.com/dylibso/chicory/tree/main/wasi. We use jimfs to keep things simple and secure (and not worry about exposing the real filesystem): https://github.com/google/jimfs When I did this experiment a few months ago, what we could accomplish was pretty limited. I could load and query databases, but not write to them. However the Chicory wasip1 implementation is advancing. BTW, we've borrowed a few ideas from wazero so thanks for your work there :)