lwjgl3ify VS Quarkus

At least you can now run Minecraft 1.7.10 on Java 17 - https://github.com/GTNewHorizons/lwjgl3ify

The "backport" in question is lwjgl3ify, plus a fuckton of forks of ancient mods + endless mixins into ARR mods in the form of Hodgepodge.

GTNH does have a way to run new Java on 1.7.10, probably can be ported to other versions too ;) https://github.com/GTNewHorizons/lwjgl3ify

It's called lwjgl3ify

Adding a new SectionHelper is not hard. Of course this sample is naive, and the complexity hidden in the converter. But I am sure you can foresee useful use cases for them. Everything I've just shown is available with Quarkus and Qute only.

• GraalVM Official Website: https://www.graalvm.org • Native Image Documentation: https://www.graalvm.org/reference-manual/native-image/ • Spring Native Project: https://spring.io/projects/spring-native • Quarkus Framework: https://quarkus.io • Micronaut Framework: https://micronaut.io • Oracle Substrate VM Paper: https://www.vldb.org/pvldb/vol10/p1138-vincent.pdf • “Fast Startup for Java” by Cristiano Betta (Conference Paper) • OpenTelemetry Java Native Image Support: https://opentelemetry.io/docs/java/nativeimage/

Having been in development for a long time, no.

Frankly, it just takes some motivated senior devs and the tantalizing ability to put out the OP blog post and you've got something management will sign off on. Bonus points you get to talk about how amazing it was to use Apple tech to get the job done.

I don't think they seriously approached this because the article only mentioned tuning G1GC. The fact is, they should have been talking about ZGC, AppCDS, and probably Graal if pause times and startup times were really that big a problem for them. Heck, even CRaC should have been mentioned.

It is not hard to get a JVM to startup in sub second time. Here's one framework where that's literally the glossy print on the front page. [1]

[1] https://quarkus.io/

I read about how Quarkus is a Kubernetes-native Java framework designed for building fast, lightweight microservices. What’s even better is that it is optimized for cloud environments, including features like fast startup times, low memory footprints, and support for both imperative and reactive programming models.

Quarkus is a Kubernetes-native Java stack tailored for GraalVM and OpenJDK HotSpot. Quarkus offers incredibly fast boot times, low RSS memory consumption, and a fantastic developer experience with features like live coding.

In this application, we will create products and retrieve them by their ID and use Amazon DynamoDB as a NoSQL database for the persistence layer. We use Amazon API Gateway which makes it easy for developers to create, publish, maintain, monitor and secure APIs and AWS Lambda to execute code without the need to provision or manage servers. We also use AWS SAM, which provides a short syntax optimised for defining infrastructure as code (hereafter IaC) for serverless applications. For this article, I assume a basic understanding of the mentioned AWS services, serverless architectures in AWS, Quarkus framework and GraalVM including its Native Image capabilities.

At Project Au Lait, we are developing and publishing an open-source asset called SVQK, which combines Svelte (Frontend) and Quarkus (Backend) for web application development. The asset includes automated testing tools and source code generation tools. This article introduces an overview of SVQK. (For instructions on how to use SVQK, refer to the Quick Start.)

Since a few years now, we started to design various cli for internal batch usage, on our Java Stack on top of picocli and quarkus, delivered as images, and run on podman.

Quarkus is designed from the ground up for Kubernetes, serverless, and GraalVM. It's not just an alternative; it's a different philosophy.

Quarkus Official Documentation