Java 27 already? I just learned about Java 26. But I’m not complaining, the JEPs that is getting introduced on every release are quite exciting features. I highly recommend following the Java official YouTube channel, they publish entertaining, yet informative videos/shorts about tips/tricks/features.
Java 27: What's New?
11–20 of 64 posts
Re: Java 27: What's New?
#12Does the website have geoblocking or did HN gave it a hug of death?
Re: Java 27: What's New?
#13Earlier 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…
It's too many releases now. At some points, the numbers just become noise. I think most people will stick to the LTS releases, but even those come out every two years.
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.
Re: Java 27: What's New?
#14Earlier 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…
It's too many releases now. At some points, the numbers just become noise. I think most people will stick to the LTS releases, but even those come out every two years.
The current numbering scheme is annoying and distracting, bears no information yet is still error prone.
Re: Java 27: What's New?
#15Earlier 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…
It's too many releases now. At some points, the numbers just become noise. I think most people will stick to the LTS releases, but even those come out every two years.
Re: Java 27: What's New?
#16Earlier quoted context omitted.
It's too many releases now. At some points, the numbers just become noise. I think most people will stick to the LTS releases, but even those come out every two years.
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.
Re: Java 27: What's New?
#17Re: Java 27: What's New?
#18Earlier quoted context omitted.
It's too many releases now. At some points, the numbers just become noise. I think most people will stick to the LTS releases, but even those come out every two years.
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.