For those of you who can't wait any longer I just pushed MOE 2.0.0-alpha-1.
The proper announcement / docs / source code will appear over the next days, but for the adventurous types here are the coordinates:
git clone https://github.com/multi-os-engine/moe-samples-java -b moe-master
git clone https://github.com/multi-os-engine/moe-samples-kotlin -b moe-master
I can't stress this enough: this is an unstable development release, an Alpha version. Do not use it for production.
You should be able to run the samples the way you did with MOE 1.3. Upgrading a project from 1.3 to 2.0-alpha should be the same process as you had with the 1.3-beta -> 1.3 upgrade: update the gradle plugin version, and run the Xcode config updater from your IDE (New feature: now we have a Gradle task for this as well!). You should not get any troubles with this, please let me know if you run into anything. (LibGDX is largely untested, so there could be some dragons / flappy birds... )
Known limitations (among many others, but these are the ones everyone is talking about):
- Binary size is larger than with MOE 1.3. Size optimization will be one of the next steps, I will make a detailed post about this in the next days.
- Performance is better than MOE 1.3 on some benchmarks, but others are worse. Overall a bit better on the SciJava benchmark. I will also make a detailed post about performance, and why you should not care about it too much now
- Build times (particularly if you enable ProGuard (which you shouldn't for now, if you are in a hurry, or don't want your computer to glow white hot ). Well, Jack (and in some part LLVM) has to take the blame for this one. We already have the plan to migrate from it, can you guess what I am going to say about "making a detailed post" .
- Remote build is not supported now, you will need a Mac for MOE 2.0 at this time.
Enjoy (or better: wait for the proper announcement and docs ) ,