Design Patterns VS Codename One

After that, more practice, and then Design Patterns (as in the famous book of the "Gang of Four": "Design Patterns: Elements of Reusable Object Oriented Software"). Here I'd recommend "Head First: Design Patterns" and Java Design Patterns as well as Refactoring Guru (the sites are more reference than course).

For Design Patterns - any resource recommendation that misses Java Design Patterns and Refactoring Guru (also for Refactoring) as well as *Head First: Design Patterns, has failed.

A massive list of design patterns and how they could be implemented (in Java) can be found here.

https://java-design-patterns.com/ has example code for things like object pools that can help with memory management.

Sidenote: I would not really use the GoF Design Patterns book anymore. Too dry. I would use "Head First: Design Patterns" - much more modern, much easier to read, or Refactoring Guru or Java Design Patterns (uses Java, but again, only for illustrations).

Also: https://java-design-patterns.com and https://refactoring.guru/design-patterns

Use either Java Design Patterns or Refactoring Guru. Both resources are far higher quality than yours.

Java Design Patterns

Java Design Patterns - IMO one of the most accessible sites with very easy explanations

A hint: go to Java Design Patterns and go through the patterns to figure what could fit.

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.