jsweet VS j2cl

You can take a look at https://github.com/j4ts, which contains some Java libs transpiled by JSweet to TS/JS. The AWT/Swing implementation is just a proof of concept, but some other libs are fully functional like awt/geom.

However, you have to be aware that the initial purpose of JSweet was not to port all Java libs to JS. JSweet allows the transpiler to be customized (with extensions) to map Java APIs to JS ones so that you don't necessarily need a JS runtime. It's all explained in the "Extending the transpiler" section of the core doc: https://github.com/cincheo/jsweet/blob/master/doc/jsweet-lan...

We used a lot GWT with UI frameworks like dominokit or Vaadin. There is another transpiler not mentioned before: https://github.com/cincheo/jsweet It has better JS ecosystem integration and some library ports. I never used it, but it worth to try.

Well, you can, in theory use any language if you transpile it - that way, you'd end up using a single language across the stack (even if you're technically using JS). An example of this would be JSweet.

TheVirtual FTC simulator team is looking for FTC team members or alumni who want a programming challenge. We want your help adapting jsweet https://www.jsweet.org/ to transpile Java code to JS. Programmer will be working on automatic translation of Java to Javascript. Experience with both Java and Web development is ideal.

Definitely worth a look thank you! On another note, I've experimented successfully with https://www.jsweet.org/.

I look forward to getting back into front-end if I can do it in Java only (which can be done today) ... and not be looked down upon by frontenders, the CSS tricks designer crowd and the highly vocal JavaScript crowd.

www.jsweet.org

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