teavm VS SnapKit

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.

SnapCode is actually using SnapKit (https://github.com/reportmill/SnapKit) which can run on either WebAPI/DOM (in browser) or Swing (desktop). In the browser this helps slim the download and improve performance by using more browser native code.

For pricing, SnapCode is free for individual use and will remain so. Perhaps there will be funding opportunities from large organizations or for embedding use cases to help provide for the continued health of the product and community.

The new kid on the block is SnapKit: https://github.com/reportmill/SnapKit

Theres a bit more to it than that, since you want resetUI to update all of your components without triggering respondUI(). And you want all your components to be automatically configured to call respondUI() when there is user interaction.

I’ve written one of these before, but I don’t have access to a public version anymore. I do all my current UI dev in a UI kit built on top of Swing. But here is what I use there that solves this problem:

https://github.com/reportmill/SnapKit/blob/master/src/snap/v...

I use SnapKit to do Java desktop development which compiles easily to JavaScript using TeaVM. SnapKit is both modern and conventional, a good middle ground between Swing and JavaFX. But most importantly, it combines the traditional win of desktop Java UI dev with the ease of web deployment.

    SnapKit: 

Repo: https://github.com/reportmill/SnapKit