wasmedge-quickjs VS teavm

I'm impressed you're already leveraging the component model. I thought it wasn't quite ready for primetime yet, but it seems you're proving that wrong... I'll have to dig in more here, as I'm working embedding WebAssembly in a high performance storage engine.

Thanks for the notes! I hear you on QuickJS - I've seen approaches of folks trying to build more node compatibility on top of quickjs (ala https://github.com/second-state/wasmedge-quickjs), but have recently heard about spidermonkey in wasmtime. Do you have intuition for nodejs vs browser in terms of what people want in terms of compatibility?

"A high-performance, secure, extensible, and OCI-complaint JavaScript runtime for WasmEdge. Run JavaScript in WebAssembly" wasm-edge-quickjs

See potential problems #1 for its proposed changes https://github.com/second-state/wasmedge-quickjs/pull/82#iss...

https://github.com/second-state/wasmedge-quickjs/pull/82#iss...

Try the bot on a PR you're interested in:

I can conceptualize a way to convert JavaScript source code to WASM then convert WASM to C source code. I have considered just using WASM, however, that introduces yet another runtime to manage https://github.com/second-state/wasmedge-quickjs.

Technically you can create a C shared object and import that shared object into QuickJS, see https://github.com/rsenn/qjs-modules, also https://github.com/second-state/wasmedge-quickjs.

That was achieved with QuickJS here https://bellard.org/jslinux/vm.html?url=alpine-x86.cfg, and here https://github.com/second-state/wasmedge-quickjs.

WasmEdge provides excellent support for JavaScript, including ES6 and NPM modules, async networking, the fetch API, React SSR, and even mixing Rust code with JS code. https://github.com/second-state/wasmedge-quickjs

Joel from our team worked on the initial prototype for WASI support in TeaVM (https://github.com/konsoletyper/teavm/pull/610), and we temporarily forked before the WASI support made it to the official repo.

Good reminder to deprecate that now!

A number of concerns with the viability of the current WASM GC are covered here (Google translation to English):

https://habr-com.translate.goog/ru/articles/757182/?_x_tr_sl...

and the original article:

https://habr.com/ru/articles/757182/

This is from the author of TeaVM, who has 10 years of experience getting Java and JVM code to run efficiently in the browser. https://teavm.org/

TeaVM's existing transpilation of Java to JavaScript performs well (using the browsers JS GC). It will be interesting to see if WASM GC matures to the point where it is even faster.

Uses this apparently: https://github.com/konsoletyper/teavm

How does this compare to say the TeaVM (https://github.com/konsoletyper/teavm) which I know only has "experimental" WASM support at the moment?

For Java, no WASM file is requested. Maybe the Java code was transpiled to JavaScript, perhaps using TeaVM.

>> It's not like you can take a random JAR and convert it to WASM.

Maybe you can:

TeaVM is an ahead-of-time compiler for Java bytecode that emits JavaScript and WebAssembly that runs in a browser. Its close relative is the well-known GWT. The main difference is that TeaVM does not require source code, only compiled class files. Moreover, the source code is not required to be Java, so TeaVM successfully compiles Kotlin and Scala.

https://teavm.org/

I have never had an opportunity to try out TeaVM, but it seems promising.

For a fast, lightweight, Java-based front-end, try TeaVM and its Flavour toolkit:

https://teavm.org/

It is easy to get started by using the maven archtetype, there's an tutorial in Java Magazine here:

https://blogs.oracle.com/javamagazine/post/java-in-the-brows...

With TeamVM and Flavour you get a full front-end SPA framework that lets you code business logic in Java, and pair that with HTML and CSS to make components.

To see what it can do, check out Wordii, a fast-paced 5-letter word game:

> Someone will make the JRE run on WASM

https://teavm.org/

Minecraft contains some native dependencies, though; you'll need something like https://copy.sh/v86/ or https://bellard.org/jslinux/ with the right operating system image to run it in browser.