Why Dropping Java 8

This document explains what Quarkus would benefit by dropping Java 8.

Please fill it in as you find ideas, but keep it focused on the technical reasons: the APIs offered by Java 11 which make it compelling enough to drop Java 8 compatibility.

Not asking about the JVM runtime

Many have been keen to point out the benefits of running a Quarkus application on JVM11 (or later), however you can do so even if Quarkus maintains compatibility with Java 8.

Quarkus already is fully compatible and regularly tested with both Java 8 and Java 11 (as runtime).

We are specifically exploring reasons to require Java 11 as base, which would imply dropping compatibility with Java 8. So please focus on the SDK API.

Not asking about workarounds

In many cases it is possible to craft code to actually use minor improvements coming from the Java 11 (or later) SDKs, such as using multi-release jars or other tricks.

We’re aware that such options exist, but they come at a complexity cost:

• more complex implementation

• much harder to support

• harder to maintain

So the benefit of using such workarounds can only be justified on specific high-value cases, and more generally is dubious and we still want to explore the option of simply require Java 11 instead.

Good reasons to require Java 11

---

So far we didn’t identify many strong reasons. Please edit and add!

---