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

Java 27: What's New?

loicmathieu.fr

Post reply on HN
Print view View original

21–30 of 64 posts

Re: Java 27: What's New?

#21

Post by mountainriver »

doikor wrote: post #5
zelphirkalt wrote: post #3

Is it just my personal feeling, or are Java version numbers becoming as inflationary as browser version numbers?

They moved to a schedule instead of waiting for features to be finished. Basically we get a new major version release on a schedule. Everything that is finished gets packaged in and everything else pushed to the next release. The issue before was that they marked beforehand "version X will contain feature Y" and then feature Y got delayed by 3 years which means everything else in version X also got delayed by 3 years…

Do they have backwards compatibility guarantees?

Otherwise what are we doing here?

Re: Java 27: What's New?

#23

Post by wtetzner »

robertjpayne wrote: post #16
OtomotO wrote: post #13

Earlier quoted context omitted.

Unless you're forced at gunpoint, how can there be too many releases? Rust releases every 6 weeks, since 2016... If you don't want to update, just don't? If you feel (!) pressured, you should work on that.

Rust releases are just compiler toolchain, maybe some new syntax features. Java includes the JVM which is subject to way more security issues and needs much more frequent updating.

But can't you continue to run older bytecode versions on newer JVMs? I think you can also specify the source version separately.

Re: Java 27: What's New?

#24

Post by mountainriver »

The best thing to ever happen to the software world was Oracle buying Sun and consequently Java.

Java was great at its time but then had to go. Oracle gaining control over them sped up this process.

Poor Android got caught up and now half our phones don’t work

Re: Java 27: What's New?

#26

Post by cogman10 »

mountainriver wrote: post #21
doikor wrote: post #5

Earlier quoted context omitted.

They moved to a schedule instead of waiting for features to be finished. Basically we get a new major version release on a schedule. Everything that is finished gets packaged in and everything else pushed to the next release. The issue before was that they marked beforehand "version X will contain feature Y" and then feature Y got delayed by 3 years which means everything else in version X also got delayed by 3 years…

Do they have backwards compatibility guarantees? Otherwise what are we doing here?

They do, some of the best of any language.

That said backwards compatibility problems still hit as some libraries enjoy using internal APIs.

It's not an every time thing and it's been easier and easier with updates.

Re: Java 27: What's New?

#27

Post by collabs »

mountainriver wrote: post #21
doikor wrote: post #5

Earlier quoted context omitted.

They moved to a schedule instead of waiting for features to be finished. Basically we get a new major version release on a schedule. Everything that is finished gets packaged in and everything else pushed to the next release. The issue before was that they marked beforehand "version X will contain feature Y" and then feature Y got delayed by 3 years which means everything else in version X also got delayed by 3 years…

Do they have backwards compatibility guarantees? Otherwise what are we doing here?

I work with dotnet but my understanding is that some applications/ teams are still on java 8 with spring boot or whatever so it isn't like they aren't modernizing but they are choosing to do so at their own time which is fine I think

Re: Java 27: What's New?

#28

Post by UltraSane »

mountainriver wrote: post #24

The best thing to ever happen to the software world was Oracle buying Sun and consequently Java. Java was great at its time but then had to go. Oracle gaining control over them sped up this process. Poor Android got caught up and now half our phones don’t work

What are you trying to say?

Re: Java 27: What's New?

#30

Post by pgwhalen »

ptx wrote: post #18
OtomotO wrote: post #13

Earlier quoted context omitted.

Unless you're forced at gunpoint, how can there be too many releases? Rust releases every 6 weeks, since 2016... If you don't want to update, just don't? If you feel (!) pressured, you should work on that.

With each new Java release the previous one becomes instantly unsupported (meaning that it receives no security updates), unless you pay Oracle (or another vendor). So you are forced to update if you want security updates (or run only LTS releases, or pay a vendor).

So if the matters to you, run the LTS release, right? I'm not sure I follow the concern.
Post reply on HN