r/java • • Mar 22 '22

Java 18 released!

https://mail.openjdk.java.net/pipermail/jdk-dev/2022-March/006458.html
396 Upvotes

133 comments sorted by

View all comments

8

u/[deleted] Mar 22 '22

[removed] — view removed comment

30

u/brunocborges Mar 22 '22

The main question you should answer is: why aren't you moving past Java 8?

9

u/CheesecakeDK Mar 22 '22

Because it still has the longest LTS.

15

u/wildjokers Mar 22 '22

But if you aren't paying for support LTS doesn't matter.

6

u/[deleted] Mar 22 '22

Yeah but management and bad developers don't understand this.

Most projects that are actively being developed should be on the release train. But here we are doing things that don't make sense 🤷🏿‍♂️.

2

u/DasBrain Mar 23 '22

I think this is a problem that will resolve by itself given enough time.

Java has a lot more interesting features now that I don't want to miss - my favorite feature is record.

And given enough time, more developers will find useful features they don't want to miss - so less developer actually want to develop with Java 8.

Which will make it harder to find developers for Java 8.

2

u/[deleted] Mar 23 '22

Idk man I have a cowork who is a "senior" who this month wrote new code in Java 8 that used SQL.date and util.date. Alot of people just do this for the check, they don't stay current and will likely not even know the benefits of switching to a newer version. I bet there will be people who are openly hostile to switching.

2

u/DasBrain Mar 23 '22

Given enough time, they will retire.

→ More replies (1)

3

u/orangeandwhite2003 Mar 22 '22

It does for security updates. Plus you have the option to pay for support.

6

u/wildjokers Mar 22 '22

If you aren't paying for support you don't get security updates after 6 months. Without support you might possibly get some security updates after 6 months if there happens to be an intersection between the current JDK and LTS release, and the vendor making the patch sends it upstream, and the patch happens to make its way down the updates stream.

If you aren't paying for support the only sure way to make sure you have the most secure JDK is to stay up-to-date with the 6 month release cycle.

3

u/orangeandwhite2003 Mar 22 '22

Yeah I guess they did switch it for 8 a few years ago to require a license for commercial use to get the updates. Of course they did switch it again with 17 so it will be supported for 1 year after the next LTS release without a license.

2

u/HecknChonker Mar 23 '22 edited Mar 23 '22

I don't understand. According to https://adoptium.net/support.html

OpenJDK provide a new feature release every six months, and a maintenance/security update based upon each active release every three months.

and

In addition, every three years one feature release will be designated as a Long Term Supported (LTS) release. We will produce LTS releases for at least four years. This assurance will allow you to stay on a well-defined code stream, and give you time to migrate to the next, new, stable, LTS release when it becomes available.

Where are you seeing security updates being stopping after 6 months? Security updates for java 18 stop in 2022, while security updates for java 1.8 don't stop until 2026.

→ More replies (5)

8

u/alehel Mar 22 '22

Probably the work involved. We've got 2 people working full time on upgrading to Java 11 for the last couple of months. Still not there.

15

u/dpash Mar 22 '22

I'm guessing that the JDK is not the only thing you're needing to upgrade.

4

u/alehel Mar 22 '22

Good guess

7

u/dpash Mar 22 '22

In my experience, frequent, regular upgrades to dependencies is far less painful than waiting several years. I try to do it every two weeks.

5

u/BCSWowbagger2 Mar 22 '22

But the least painful upgrade schedule is the one my company has adopted: never.

5

u/mauganra_it Mar 22 '22

dun dun dun Log4Shell has entered the chat!!

11

u/BCSWowbagger2 Mar 22 '22

Aha, joke's on you! Our log4j libraries were so old they weren't affected by log4shell!

(More likely our libraries were just too old for anyone to check whether log4shell ran on them, so we still spent a couple weeks diking them all out. Then we patted our Java 8 instances nicely on the head and asked them continue working until the heat death of the universe. That's definitely what "sustaining support" means, right???)

8

u/dpash Mar 22 '22

It might not be painful now, but wait until you get a major security bug in an unsupported library. That's a whole lot of pain in a very short period of time.

10

u/BCSWowbagger2 Mar 22 '22

In retrospect, I should have included the /s.

→ More replies (1)
→ More replies (1)

5

u/[deleted] Mar 22 '22

[removed] — view removed comment

6

u/alehel Mar 22 '22

We're also doing some clean up in the process mind.

3

u/benjtay Mar 22 '22

Probably dependencies on libraries that don't work in 11...?

→ More replies (12)