Codename One VS Taiga

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.

I'll also check out plane.so and taiga.io. I have not checked those out.

My team at work uses taiga

taiga.io — Project management platform for startups and agile developers, free for Open Source

The folks being Penpot also make a kanban management tool, kind of like Trello, called Taiga: http://taiga.io/ And it's also OSS.

I'm rooting for both of these, and now that they have some funding I hope they'll dedicate effort on polishing the rough edges (and do something about gratuitous amount of white space that permeates all of their web presence, and maybe reconsider their color pallete). They're very close, so I think and hope we'll some wonderful results very soon.

Taiga - Storage limitation

taiga.io has been good in my experience

^ This installs docker first (not sure if needed, but I'm trying to figure out how to set up taiga.io on my k3s cluster and they seem to want docker?

Do you have to use Windows? :s Sure it'll work but it's not because you can that you should... Anyway, I looked a bit at their docker-compose, it is a very complicated app, so Docker is definitely the way to go but maybe you should get the hang of it with the base nginx image, then build your own image just serving simple stuff, because it might seem a bit overwhelming to start with something as advanced as taiga.io. Of course, looking at the myriad of docker tutorials out there might help tremendously, too.