Codename One VS Modern Java - A Guide to Java 8

codenameone.com — Open source, cross-platform, mobile app development toolchain for Java/Kotlin developers. Free for commercial use with an unlimited number of projects

This was resolved in this issue: https://github.com/codenameone/CodenameOne/issues/3706

Naturally depends on the use case, yet they work good enough to be in business for 20 years.

https://www.ptc.com/en/products/developer-tools/perc

https://www.aicas.com/wp/products-services/jamaicavm-tools/

https://www.codenameone.com/

Android 5 & 6 (only changed back into JIT/AOT due to long compile times), https://www.infoq.com/news/2014/07/art-runtime/

Unfortunely the best well known, Excelsior JET, is no longer in business, most likely due to GraalVM and OpenJ9 being available as free beer, while PTC, Aicas Codename One are safe in their domains.

There is also RoboVM (https://github.com/MobiVM/robovm) as free beer, however it actually started as a commercial product, and the acquisition from Xamarin kind of stagnated it (naturally).

At Codename One, we were using App Engine when our daily billing suddenly skyrocketed from a few dollars to hundreds. The potential cost was so high it threatened to bankrupt us within a month. Despite our best efforts, including educated guesses and fixing everything we could, we were never able to pinpoint the specific bug. Instead, we had to solve the problem through brute force.

We don't use GraalVM since our project was developed prior to its existence and we aimed for deeper native integration than it can offer: https://github.com/codenameone/CodenameOne

XMLVM, Codename One and iSpectrum (cross compile Java code from an Android app or creating one from scratch

I suggest filing an RFE in the issue tracker.

Thanks. It's always good to get another reminder. Yes, it was reported. u/shannah78 is working on this but we have time until November.

please check this issue https://github.com/codenameone/CodenameOne/issues/3686

We use ParparVM which we wrote. It compiles a subset of Java 8 (sort of) to native by translating the bytecode to C and passing that through XCode. The reason we took this path and not the path of "direct to native", is that it allows for future compatibility.

Here are some resources I've found helpful and have read or are on my backlog to catch up with these developments:

- https://github.com/wesleyegberto/java-new-features (terse, includes links to JEPs, good jumping off point)

- https://github.com/winterbe/java8-tutorial (quick tour through features of Java 8)

- https://winterbe.com/posts/2018/09/24/java-11-tutorial/ (same for Java 11)

Books:

- Java 8 in Action / Modern Java in Action (Raoul-Gabriel Urma, Alan Mycroft, Mario Fusco; 2014 and 2018 respectively)

- The Well-Grounded Java Developer (Martijn Verburg, Benjamin Evans, Jason Clark; 2022) - not specifically focused on new features but does cover them in the context of going deeper into Java and the JVM.

Otherwise, learning Maven has been really important. As for learning the language, I liked Winterbe's guides. Here's one. https://github.com/winterbe/java8-tutorial