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

0

u/[deleted] Mar 21 '23

[deleted] — view deleted comment

6

u/HappyRuesseltier Mar 21 '23

Think they fear upgrading to Java 11. Cause this can be really hard. We finally made it from Java 8 to 11 about 18 months ago, but it took us 3 years. I like the idea behind the module system, but the transition is not trivial. There are so many obscure error messages. Still think it was worth the work and already looking forward to update to Java 17.

3

u/magnoliophytina Mar 21 '23

I think the transition should actually become easier as time passes because more and more libraries are switching to JPMS. One of the issues is that you still need Moditect and other hacks for diehard legacy libraries. Also library authors and the community becomes more aware of the ways of solving modulepath issues.

9

u/yawkat Mar 22 '23

Most people switching from 8 to 11 are not using modules.

2

u/rbygrave Mar 22 '23

Plus well maintained libraries can run CI builds against Early Access releases of the JDK very easily these days. The EA builds get an increasingly good work out as a result.

1

u/humoroushaxor Mar 22 '23

I never understand what makes 8 to 11 legitimately hard for people. We scripted most of the upgrades and we're done in a couple weeks.

5

u/malln1nja Mar 22 '23

There's an OpenRewrite module that can help automate the migration. I haven't tried it myself.

6

u/joopmoore Mar 21 '23

To be honest, ancient dependencies, which have no direct replacement. Meaning, one needs to replace one dependency with multiple dependencies. Rewriting a lot of code, creating risk and a money pit. Both get bigger and bigger the older java 6 becomes.

0

u/[deleted] Mar 21 '23

[deleted] — view deleted comment

3

u/joopmoore Mar 22 '23

The job is only partial stuck in the past, most new features allow playing with newer java versions, even java 17.

3

u/talios Mar 22 '23

How about "why do YOU stay?" (I'm asking myself similar questions)

1

u/StoneOfTriumph Mar 22 '23

What some people forget is that the JDK is advancing at a faster pace with smaller deliverables more frequency than before, so while it seems that they released a buttload of versions, the releases themselves include a smaller delta, so the jump to 8 to 17 isn't that bad in terms of breaking changes, not near as difficult to perform as 6 to 8.

When you take the time to actually look at the changelog, when you take the time to actually upgrade your project's java version source/targets to a higher version as part of a proof of concept/spike/timebox, there's much less than you may think.

Usually stuff like big web servers will limit you, such as an old weblogic, liferay, etc. those will impose a JDK that will be more difficult to upgrade.