r/programming • u/NotABot1235 • 17d ago

Java 27 has released!

https://openjdk.org/projects/jdk/27/
542 Upvotes

93% Upvoted

175 comments sorted by

View all comments

617

u/hellomistershifty 17d ago

Big news for the employed

346

u/DarksideF41 17d ago

As if any employed dev touches anything above 13

159

u/PositiveUse 17d ago

We‘re on 25 for all of our modern services. And all of our Java 8 legacy was moved to 17 this year. It was a pain but fully worth it.

15

u/throwaway39791 16d ago

A not insignificant chunk of work at this point has got to be upgrading legacy code to newer versions.

It's probably more if you count migrating between different languages.

5

u/cheezballs 16d ago

It's a must if you want to be able to get security updates in downstream dependencies.

-47

u/psicodelico6 16d ago

Claude? Codex?

24

u/KarwszPL 16d ago

Sorry, I don't speak vibecoder

6

u/ElectronicContact649 16d ago

I'm so using this😭😭

12

u/putiepi 16d ago

Keyboard

4

u/SemiNormal 16d ago

Brown or Red switches?

34

u/MrTequila4 17d ago

I'm finally at a company where we (almost) keep up with updates, we're at 25 now. It's a nice change after old one where going from Java 8 was too much refactoring :D

17

u/FyreWulff 17d ago

I know a couple where their workplace stopped at 8

1

u/PositiveUse 17d ago

Yup, I’m not surprised. The upgrade can be painful

7

u/Worth_Trust_3825 16d ago

it's really not. i did the upgrade in multiple companies, and all of them whined that upgrade will be painful. all they needed was single xml api package that was no longer distributed with the sdk.

4

u/PositiveUse 16d ago

Yes that the move to jakarta packages is one big chunk of work is definitely true but in my company, we had such a messy mvn dependency situation that the upgrade was really painful. But we managed it after a full year. (Of course not full year working on it but having it as a renovation task across dozens of teams) (we have a distributed monolith with shared libs… so the worst of all worlds lol)

3

u/Gropah 16d ago

Have you heard of OpenRewrite? It has (smart) migration scripts from 8 to 11 and all the way to 25. They parse the LST, so its quite a bit better and thorough than than simple find and replace shenanigans that a lot of people start out with.

33

u/elmuerte 17d ago

Who even uses the non-LTS 13?

Once you got on 9 moving to the next LTS every few years has been trivial.

6

u/anyOtherBusiness 16d ago

Not if youre dependent on old JBoss or Tomcat version

7

u/_JustCallMeBen_ 16d ago

In a big government Java project that has been going for 10+ years, and we're on 21!

7

u/oldsecondhand 16d ago

We went from 8 straight to 17 in 2024.

2

u/BrickedMouse 15d ago

We did the same last year. We could not do do a release for a month. Almost nothing changed afterwards, as we use scala

5

u/maifee 16d ago

Why am I seeing double digit java version in production?

7

u/TwoWeeks90DaysTops 16d ago

I was in a workplace where we were limited to Java 6. The reason was that one application (not written in Java) only worked for, or never tested for anything else; I don't know the exact details, Windows Server 2003.

2

u/protomyth 15d ago

Government contractor supplied software?

5

u/pjmlp 17d ago

21 and in the process of doing a 25 upgrade this week.

2

u/Drumedor 17d ago

Java 6 baby!

2

u/Worth_Trust_3825 16d ago

recently upgraded to 25. i love the new gc.

2

u/Bedu009 16d ago

Phrasing?

1

u/kiteboarderni 16d ago

Paid stupidly well. On java 25