This page compares OverrunGL with LWJGL 3.

Pros

No JNI

OverrunGL uses the FFM API instead of JNI, which is designed to enables Java programs to use native libraries and process native data without the brittleness and danger of JNI.

No NIO buffers

OverrunGL uses MemorySegment instead of NIO Buffers, which not only expands the accessible range of memory to long, but also avoids annoying flip and clear methods.

No long pointers

OverrunGL uses MemorySegment instead of long to represent memory addresses, which distinguishes addresses from numbers.

Cons

Less bindings

OverrunGL is still at its beginning, and there are only a few supported bindings.

If you need a new binding, please create a feature request.