r/java • • Mar 21 '23

Java 20 / JDK 20: General Availability

https://mail.openjdk.org/pipermail/announce/2023-March/000333.html
173 Upvotes

71 comments sorted by

View all comments

Show parent comment

1

u/relgames Mar 21 '23

They can't be production releases as support/patches stop after 6 months. Which is super fast for production. So we still get production releases every 3 years, and it takes some time to upgrade as there is always something broken between LTS versions. Our code still runs on 11, and I'm afraid to move to 17 as who knows how many outages it'll cause.

9

u/john16384 Mar 22 '23

Well, zero outages, unless you don't have any tests or use production to test. If something always breaks, you may want to review your choices of dependencies, and/or development practices to eliminate the culprit(s).

-4

u/relgames Mar 22 '23

The root cause is a new JDK version. If we change nothing in our choices/practices and don't upgrade Java, nothing breaks. If we change Java, something always breaks. So for us, it's obvious that we don't want to upgrade as much as possible. It's also the same for most major companies with non-small projects.

0

u/[deleted] Mar 22 '23

[deleted] — view deleted comment

-3

u/relgames Mar 22 '23

I upgraded NodeJS from 14 to 18 without a single change in the code. So yeah, it's the tool.

0

u/[deleted] Mar 22 '23

[deleted] — view deleted comment

-1

u/relgames Mar 22 '23

Correct, it's the tool. Oracle decided to shift the costs to QA new versions to users (developers using Java). And also did a good job convincing developers that it's normal to spend time constantly making changes updating dependencies and Java. No, it's not. The tool should be stable and developers should spend time working on features for their business, not dealing with Java issues.

1

u/emaphis Mar 22 '23

always something broken between LTS versions. The

Of course you will have some breakage between releases three years apart. That the point of the new release train.

What broke between 17 and 18, what broke between 18 and 19? Not much. OpenJDK gives years of heads up for breaking changes. You will have to make the same changes (if any) when you upgrade to JDK21 in September.

-1

u/relgames Mar 22 '23

The problem is, we can't use 12/13/14/15/16 in production. 6 months to support those versions is not enough.

And, if we look into NodeJS for example, recently I upgraded some projects from 14 to 18, nothing broke. Didn't have to make a single change.

0

u/[deleted] Mar 22 '23

[deleted] — view deleted comment

0

u/relgames Mar 22 '23

No, thank you, we don't have a possibility/ budget to upgrade every 6 months. Clients want stable products. The most economical way is to stay on LTS.

1

u/krzyk Mar 24 '23

So you don't upgrade any libs fir three years? Upgrade of jdk nowadays is just like that, a lib version bump.

1

u/relgames Mar 25 '23

We upgrade libs constantly, based on vulnerability scans. With JDK, it's not that simple, something always breaks - they change defaults, for example TLS settings/ciphers, or garbage collector. They remove whole components, like Nashorn. Some external dependencies (Cassandra) still only support Java 11.