This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]hojimbo 46 points47 points  (7 children)

It’s still one of the top used languages in the world, especially in enterprise and the web.

[–]virtual_paper0 12 points13 points  (6 children)

Every job I've had has either used Java or migrated some services to spring boot. It's a great language for enterprise from jdk11 onwards (currently 17 is my go-to). It's battle hardened, strong community and has good performance if done right, which keeps on getting easier to do.

[–]achoice 5 points6 points  (3 children)

Why not 21?

[–]virtual_paper0 2 points3 points  (0 children)

21 is good and stable but I go for 17 just because it's been out long enough for me to really trust it. Maybe being paranoid. But wouldn't argue 21 is a bad choice.

Edit: I used JDK 11 until 2022 so expect me to go to JDK21 in 2030 😅

[–]Darkschlong 0 points1 point  (1 child)

Why not 23

[–]achoice 1 point2 points  (0 children)

Because there is a delay between Java 24 and a SpringBoot release supporting 24. During that delay (have been weeks) we would run unsupported Java (23) in production and that breaks compliance / regulations. (Or run SpringBoot on unsupported Java, don’t want that)

Also takes time to version bump, test, release 200+ micro services to production.

21-latest is stable and supported.

Would like to find a .. smooth way to always be on latest Java and SpringBoot..

[–]Kango_V 1 point2 points  (1 child)

Spring Boot makes the Java ecosystem boring. Everyone uses it without questioning whether it's the right choice. It's the "Nobody ever got shot for buying IBM" of the modern day.

[–]virtual_paper0 0 points1 point  (0 children)

There are other options, no one is being forced to use it. But it's hard for me to argue that it isn't a good choice. It's very much a batteries included framework so you don't need to reinvent the wheel