libgdx: Issues requiring a major release that won't be fixed anytime soon

What is this? Simply said, this is:

an invitation not to open new issues implying wide API breakage
a single collection point for such issues
a gentle way to let the dev team absorb the idea that sooner or later a major release will be needed ☺️

This is what I collected so far:

Immutable Color and Vector
gdx-utils
Logging (BTW I think that a logging system separated from Gdx.app, for instance Gdx.logger, would be much easier to customize)
Vulkan
For consistency’s sake use Array in place of ArrayList

About this issue

Original URL
State: closed
Created 9 years ago
Comments: 37 (27 by maintainers)

Most upvoted comments

I’m not sure what people expect from Vulkan. It’s an extremely fickle API and the gains for what 99% of libGDX users do (2D) will most likely be nil.

badlogic on Dec 10, 2016

Jack is broken in all kinds of funny ways. RetroLambda does the same thing, I’m OK with (optionally) supporting that in gdx-setup.

On Dec 15, 2016 11:46 PM, “Jakub Kerber” notifications@github.com wrote:

Speaking of Java 8 though, things have changed since the release of Android 7.0 (previously N), namely most Java 8 features are now supported on older Android versions thanks to Google’s new “Jack” toolchain, specifically:

Features requiring Android 6.0 and lower:

Lambda expressions

Method references

Type annotations

Features requiring Android 7.0 and newer:

Default and static interface methods

Repeatable annotations

All we need to do is to update our build.gradle files to allow source compatibility with JDK 1.8 and to tell the Android SDK to build with Jack (details in the link below) and we’re ready to go.

I don’t see why we shouldn’t take advantage of new features of Java 8 (specifically the new Stream utlities, which could be very useful on modern multi-core mobile devices) instead of still using a 10-year old Java version. I’m ready to take care of the necessary PR myself, as long as we all agree on this.

source: https://developer.android.com/guide/platform/j8-jack.html

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/libgdx/libgdx/issues/3494#issuecomment-267466905, or mute the thread https://github.com/notifications/unsubscribe-auth/AAfYBG4M9231aUvPkFQ_3zKE1JJrMTN7ks5rIcMpgaJpZM4GQxnW .

badlogic on Dec 15, 2016

I also want to be like all then other cool kids on the block and use lambdas.

On Thu, Apr 21, 2016 at 10:45 AM, Nicholas Hydock notifications@github.com wrote:

Something to bring up: LWJGL3 has switched over to requiring at least Java8 to build and run. Since libgdx has the LWJGL3 backend, I was wondering if is this going to impact libgdx’s build process significantly. Android has already switched over to using OpenJDK8 on newer versions of android, but with KitKat still has a large market share of android. At this point in time I feel LibGDX should require at least Java8/9 to build and run already with how old Java 8 already is, with people who wish to support older platforms having to use old libgdx. For those who need a Java8 JRE to package with their games, they can use something like Zulu on desktop.

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/libgdx/libgdx/issues/3494#issuecomment-212953598

sjosegarcia on Apr 21, 2016