LWJGL 3.3.3 Released With Updated Bindings, GraalVM Native Image Support

[timofonic]

Java is not Python.

Each release of Java is backwards compatible, Java 21 compiler can parse source/byte code from Java 1.4.

In olden days JDK compatibility issues were caused by lazy devs who thought spending 10 minutes learning an Apache library was harder than spending days hacking a jdk's internal security classes. These classes were internal and subject to heavy change, which lead to projects being locked versions of JDK.

The 6 month release cycle is a pita, but almost everyone is sticking to Long Term Support versions (1.8, 11, 17, 21).

For example Spring decided to jump from 1.6 to 17.

Planning to upgrade to the latest LTS should be part of your plans and you'll have no issues with any dependencies. Since you will either be using the same or a newer version of the JDK.

The upgrade pain is mostly the java team is pulling some libraries out of the JDK into their own libraries, so you have to add them back in.

Despite your good intentions, it sounds like desperate justification about what Java is.

It makes C++ mess look beautiful in comparison. Add Oracle to the mix and there's the perfect nightmare.

Offtopic: I'm forced to learn Java and I hate it with passion. Any advice? This is Karma...

[stevecrox]

Lightweight and Java, two words that never go hand-in-hand.

Which is sad because performance wise Java is quite on par with C++ (see this for example). The feeling of it (java) being slow is much more attributed to it being a gigantic resource hug, slow to start and these days a pain to even install. To add to this, the Sun takeover by Oracle (many years ago by now) thoroughly fucked java. I don't if it's because of them (Oracle) but the result is many "active language versions" making it difficult to run projects as each project seems to require a different java version.

Java is not Python.

Each release of Java is backwards compatible, Java 21 compiler can parse source/byte code from Java 1.4.

In olden days JDK compatibility issues were caused by lazy devs who thought spending 10 minutes learning an Apache library was harder than spending days hacking a jdk's internal security classes. These classes were internal and subject to heavy change, which lead to projects being locked versions of JDK.

The 6 month release cycle is a pita, but almost everyone is sticking to Long Term Support versions (1.8, 11, 17, 21).

For example Spring decided to jump from 1.6 to 17.

Planning to upgrade to the latest LTS should be part of your plans and you'll have no issues with any dependencies. Since you will either be using the same or a newer version of the JDK.

The upgrade pain is mostly the java team is pulling some libraries out of the JDK into their own libraries, so you have to add them back in.

[markg85]

Lightweight and Java, two words that never go hand-in-hand.

Which is sad because performance wise Java is quite on par with C++ (see this for example). The feeling of it (java) being slow is much more attributed to it being a gigantic resource hug, slow to start and these days a pain to even install. To add to this, the Sun takeover by Oracle (many years ago by now) thoroughly fucked java. I don't if it's because of them (Oracle) but the result is many "active language versions" making it difficult to run projects as each project seems to require a different java version.

[Chewi]

For those who don't know, Minecraft actually uses LWJGL, or at least it did the last time I checked.

[Ironmask]

Well, ruby and python are one of the highest performing languages ever built unlike Java. They're especially suitable for highly threaded apps unlike Java and its totally silly lack of GIL. Also Java only comes with a single toy GC that was only designed for non-interactive legacy server apps, namely the generational zgc. The latest version (21) will ship with these heavy weight fibers. Unbelievably crappy release to be honest.

I know this post is sarcastic but I legitimately can't tell what your point is.

[caligula]

I consider this and things like pygame/rubygame to be strange fascinations. People love trying to make games in/on anything, even inside other video games. It's kind of like a challenge, how far can you get into making a game in Java or Python before it becomes an unmanagble mess?

Well, ruby and python are one of the highest performing languages ever built unlike Java. They're especially suitable for highly threaded apps unlike Java and its totally silly lack of GIL. Also Java only comes with a single toy GC that was only designed for non-interactive legacy server apps, namely the generational zgc. The latest version (21) will ship with these heavy weight fibers. Unbelievably crappy release to be honest.

[Ironmask]

Who uses Java for games these days other than Minecraft, RuneScape, Wakfu, Stardew Valley, Star Wars Galaxies?

This is useless. Java is corporately owned and focused mainly for business software. It's unsuitablebfor games, at least for those complex ones requiring performance.

I consider this and things like pygame/rubygame to be strange fascinations. People love trying to make games in/on anything, even inside other video games. It's kind of like a challenge, how far can you get into making a game in Java or Python before it becomes an unmanagble mess?

[timofonic]

Who uses Java for games these days other than Minecraft, RuneScape, Wakfu, Stardew Valley, Star Wars Galaxies?

This is useless. Java is corporately owned and focused mainly for business software. It's unsuitablebfor games, at least for those complex ones requiring performance.

[cynic]

cool project, never heard about it!

[phoronix]

Phoronix: LWJGL 3.3.3 Released With Updated Bindings, GraalVM Native Image Support

Version 3.3.3 of the Lightweight Java Game Library (LWJGL) is now available for this Java library that makes it easy to utilize native APIs from OpenGL and Vulkan to OpenCL compute and other OS APIs within Java's confines. LWJGL is used for Java games and can also be used with other Java software looking for rich API support particularly around GPU integration...

https://www.phoronix.com/news/LWJGL-3.3.3