webfx VS j2cl

There's this: https://github.com/webfx-project/webfx. But it uses GWT which is not maintained (actively) anymore.

For JavaFX on web there is WebFX, Gluon Promise, and JPro.

WebFX - a JavaFX to JavaScript transpiler - can now access local files, as you can read on this GitHub discussion, with a demo on files.webfx.dev.

There is also https://github.com/webfx-project/webfx doing that: https://spacefx.webfx.dev/ compared to server-side rendering wit jpro https://demos.jpro.one/spacefx.html

It's not gluons project. And your words contradict themselves. If it is mirrored from a server, turning off the internet connection would freeze the game. It runs on the browser, and obviously it'll be cached after loading it once? Your words really make no sense. It's a good transpilation, that's why it's small... Can you just accept it? https://github.com/webfx-project/webfx

github.com/webfx-project/webfx/

There are many open source projects like, https://github.com/google/j2cl/tree/master/samples/wasm

This was a grand stroll down memory lane; having hacked Java since JDK 1.0, I've seen a lot of improvement.

An idle thought: he favors server-side rendering whereas the javascripts seem to favor client-side rendering. Along the way doing servlets, there came to be "view first" rendering, where you use serverside to paint a minimal page which, itself, uses ajax calls to fill in the blanks. I used that a lot.

It's true also that I migrated from servlets to node. But, in all of this, clojurescript erupted on the scene. And, for me, that's where the piece gets interesting: he introduces us to a java to clojurescript transpiler and tells us it was used to craft the google app suite. Now it's time to go play [1]

[1] https://github.com/google/j2cl

So it looks like we have pretty much everything except for the most important part: three.js that we can use from Java. And it’s a little bit of a complex part. To interop with JavaScript we should use J2CL JsInterop API, but there is a little problem: Closure Compiler must be able to recognize types of (most of the) three.js objects. Here we have two options:

You mean https://github.com/google/j2cl ? You understand though that these are trying to solve multiplatform in very different ways. I don't think this approach has a bright future.

Have you seen J2CL? https://github.com/google/j2cl