4 ms·
The one thing missing is the innovation happening on the Java front end. Frameworks like TeaVM (https://blogs.oracle.com/javamagazine/java-in-the-browser-with-
by TeaVMFan 6y ago
The one thing missing is the innovation happening on the Java front end. Frameworks like TeaVM (https://blogs.oracle.com/javamagazine/java-in-the-browser-with-teavm https://blogs.oracle.com/javamagazine/java-in-the-browser-wi...) let you extend your Java app all the way to the browser.
- TeaVMFan 6y agoFor more info on full-stack Java, including options for Java based single-page apps and Java-based mobile apps, visit https://frequal.com/FullStackJava/ https://frequal.com/FullStackJava/
- cromwellian 6y agoFrom that article "and produces smaller JavaScript that performs better in the browser". Not according to my benchmarks. That may be true if you use the GWT Widget library, but if you code 'to the metal' using Elemental, GWT produced substantially smaller code than TeaVM when I benchmarked it a few years ago with the Bench2D (Box2D) benchmark. Maybe it got better since then, but I doubt it given the progress GWT's successor made. Using J2CL (the successor to GWT), the following Java class public class Main { public static void main(String argv[]) { window.alert("Hello World"); } } would actually compile down to just (JS) window.alert("Hello World") TeaVM doesn't support code splitting that Both GWT and Closure Compiler support, or cross-module code motion. https://github.com/konsoletyper/teavm/issues/333 https://github.com/konsoletyper/teavm/issues/333
- koala7 6y agoYou might be interested in https://vaadin.com/ https://vaadin.com/.