Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Java 16

jdk.java.net

Post reply on HN
Print view View original

321–327 of 327 posts

Re: Java 16

#321

Post by PeterisP »

croo wrote: post #245
meddlepal wrote: post #44

Earlier quoted context omitted.

If you're doing green field JVM developer and NOT using big frameworks like Spring or an app server it is pretty safe to use the intermediate releases.

Uh, probably just my narrow corporate world view but... is there any serious development in java NOT using Spring? Time for me to learn so let me rephrase this question! Those who use java without EE or Spring framework, what are your go-to libraries? What are you using for DI / REST / ORM / Auth etc?

Different needs for different domains. For example, there's an old pack of machine learning code that I maintain, and it (and a bunch of other Java code that I see from other institutions) does not use or need DI, ORM, Auth nor proper REST, they typically handle processing of non-database data with no or minimal web interaction, and plain old objects are fine for that - if we started from scratch and chose Java instead of some other language, we would still not use Spring for that.

Re: Java 16

#322

Post by PeterisP »

krzyk wrote: post #92
KptMarchewa wrote: post #52

Earlier quoted context omitted.

If you're using "application servers" and not containers then definitely do not touch intermediate releases.

Why? I would say, try it out and see.

And what do you do if you "try it out" and some months later you identify a problem? Then you have to rewrite all the code without the new features to go back to the LTS version, and likely you'll have to downgrade or even swap out some of your dependencies. That's painful and expensive, there needs to be a very good reason to justify that risk.

Re: Java 16

#323

Post by lensopra »

vips7L wrote: post #262
kronin wrote: post #226

Earlier quoted context omitted.

Can't read whether this is sarcastic or tongue in cheek ;-) Java 11 is the newest LTS release. The next LTS release will be Java 17. Many companies won't touch anything that isn't LTS. There are still a large number of companies staying on Java 8 :shrug:

LTS doesn't exist within OpenJDK. LTS only exists if you're paying a specific provider for it.

Then what does AdoptOpenJDK mean when they label 11 a LTS release? https://adoptopenjdk.net/index.html

Re: Java 16

#325

Post by krzyk »

lensopra wrote: post #324
krzyk wrote: post #315

Earlier quoted context omitted.

OpenJDK provides that for 6 months. And then 6 months for a 17, and so on.

That's not "long term".

Don't look at version string, bu think java version "LATEST“. This will always have the bes support.

Re: Java 16

#326

Post by krzyk »

yjftsjthsd-h wrote: post #318
krzyk wrote: post #316

Earlier quoted context omitted.

Most recent java version is supported for 6 months and then the next one. Think of Java versions as patch releases for Java 8. There are minor changes between releases.

Sure, but that's regular releases, not LTS

What's the difference between LTS and LATEST?

Lack of features? Sorry they added shenandoah in JDK 11, AFTER release.

No code breaking changes? Sorry JDK 8 u2xx broke my code that worked on u6x.

Re: Java 16

#327

Post by krzyk »

PeterisP wrote: post #322
krzyk wrote: post #92

Earlier quoted context omitted.

Why? I would say, try it out and see.

And what do you do if you "try it out" and some months later you identify a problem? Then you have to rewrite all the code without the new features to go back to the LTS version, and likely you'll have to downgrade or even swap out some of your dependencies. That's painful and expensive, there needs to be a very good reason to justify that risk.

You don't need to downgrade dependencies, libs are at 8 and 11 right now and support up to 16 (e.g. jackson is I think at Java 7, and supports records from Java 16).

What kind of problem could you identify? Same might happen with LTS release (e.g. I had it in JDK 8, suddenly I wasn't able to use some crypto libs).

Fixes always go first to JDK latest, and then are backported to 11 and 8.

Post reply on HN