Replies: 3 comments 1 reply
-
As a little side-note both AWS and Azure is "pulling" (kind of) the support for Java 11 for various services. AWS Fargate for example, you can't set Java heap using Java 11, but you can using Java 17... Not sure about the underlaying functions there, but apparently something in the Java runtime making it difficult on Container (read Docker) services (which both AWS and Azure is using behind the scenes for Lambda/functions as well as container services (obviously)). |
Beta Was this translation helpful? Give feedback.
-
As somebody is heavily voting for keeping the use of Java 11: can you please elaborate your reasons? Thanks |
Beta Was this translation helpful? Give feedback.
-
This is the result per 31st of October 2023: For me it is not umambiguous enough to make the switch at the moment - I will ask the same question again next year :) |
Beta Was this translation helpful? Give feedback.
-
Currently ph-commons and all my other ph* libraries use Java 11 as the baseline, as it provides all the needed features and has nice coverage. Unfortunately, Oracle ends the premium support for Java with end of September 2023 (see https://www.oracle.com/java/technologies/java-se-support-roadmap.html ). OpenJdk will support Java 11 until October 2024 (see e.g. https://access.redhat.com/articles/1299013). Popular frameworks like Spring Boot 3.x already require Java 17 as the baseline and other frameworks are following.
Updating to Java 11 as the baseline of all the libraries would mean:
An update to Java 17 does not mean:
Edit: the vote is open until October 31st, 2023
20 votes ·
Beta Was this translation helpful? Give feedback.
All reactions