Java 27: What's New?

lloicmathieu 2 days ago 58 commentsRead Article on loicmathieu.fr

ES version is available. Content is displayed in original English for accuracy.

⚡ Community Insights

Discussion Sentiment

56% Positive

Analyzed from 815 words in the discussion.

Discussion (58 Comments)Read Original on HackerNews

jsiepkes•2 days ago

Dear diary, the year is 2094, 10 years since society collapsed. The neighbors went scavenging for food and I haven't seen them in 4 days. I fear the worst. Meanwhile, JEP 533 – Structured Concurrency still hasn't been declared stable, and it has entered its five-hundredth preview release in OpenJDK 136.

Alifatisk•2 days ago

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.

MYEUHD•2 days ago

Since 2018 they've been making two releases per year. One in March and one in September.

tpoacher•2 days ago

would you mind linking to the channel? not sure which one you mean

spreiti•2 days ago

https://youtube.com/@java?si=pN0ODGy-YLaaunIn

This is the official Java channel.

coldtea•2 days ago

I mean, just writing "Java official YouTube channel" to Google or YouTube gives it:

https://www.youtube.com/@java

exabrial•2 days ago

> On the performance side, I noted two interesting improvements:

> HashMap.putAll() now has a fast-path when the Map is a HashMap, which directly calls putHashMapEntries(), resulting in a 66-86% improvement (PR #28243);

> A new intrinsic for the AVX2 architecture has been added for binary search, resulting in a 1.5x to 2.35x improvement for arrays above a certain threshold (int=256, long=768, short=512, char=512) (PR #30612).

Ok THIS is impressive!

throwaw12•2 days ago

Give us some break we just recently migrated to Java 11 from Java 8

ivanjermakov•2 days ago

Don't be scared of a big number, since 2018 they do 2 releases each year.

exabrial•2 days ago

I laughed. Jump straight to 25 next! It's awesome!

samus•2 days ago

Just one more push to Java 17; from there on it should be smooth sailing. I hope you have built up a comprehensive regression test suite as part of the migration.

nerdile•2 days ago

> tests showed that for environments with one CPU (or fewer)

Article seems AI generated. Is there an official announcement we could be discussing instead?

stanac•2 days ago

It's probably comment on shared CPUs. Like in kubernetes where you can assign 300 milliCPUs.

I didn't read the article, it doesn't open for me (HN hug?).

atomicnumber3•2 days ago

I wonder if it's a joke about oversubscribed environments (cloud VPS) or a real remark about fractional CPU budgets in container environments

StefanBatory•2 days ago

Does the website have geoblocking or did HN gave it a hug of death?

leeter•2 days ago

Hug of death by all appearances, here's an archive link https://web.archive.org/web/20260710102120/https://www.loicm...

robmccoll•2 days ago

Non-nullable reference types at the language level? Null coalescing operator? Safe navigation accessors? Record composition?

zelphirkalt•2 days ago

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

doikor•2 days ago

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 even though they were done 6 months ago.

this_user•2 days ago

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.

bmacho•2 days ago

The numbers have become meaningless noise already. This release should've been called 26.1, then 27.0, 27.1, 28.0 and so on. Year.version. How Canonical does it with Ubuntu.

The current numbering scheme is annoying and distracting, bears no information yet is still error prone.

the-smug-one•2 days ago

Why? Just upgrade. Make it so that your org can deal with it.

OtomotO•2 days ago

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.

mountainriver•2 days ago

Do they have backwards compatibility guarantees?

Otherwise what are we doing here?

cogman10•2 days ago

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.

collabs•2 days ago

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

mkurz•2 days ago

Its just your personal feeling.

philonoist•1 day ago

You know you haven't done much if your whole HN discussion page is jokes on version number rapidly increasing and few frustrating comments on why their favorite feature is not implemented yet!

jsiepkes•1 day ago

I think you are reading way too much in those things. I made the JEP 533 joke in this thread, and I am definitely not implying progress is slow, nor am I frustrated.

I think it's a good thing the developers take their time to flesh out new features. Once it goes in, it stays like that forever. Besides, since 27 isn't an LTS release it doesn't really matter if it goes out of preview. Looking at mailingslists, etc. I can see plenty of progress being made.

mountainriver•2 days ago

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

UltraSane•2 days ago

What are you trying to say?

stanac•2 days ago

I think they are saying Java is dead?! Not sure how else to interpret the comment. If that's the case I have to disagree. There are probably billions of lines of Java in enterprise, it will never die.

chasd00•2 days ago

my standard Java analogy is it's like a garbage truck. Java is out there every day doing a job that's absolutely critical but rarely, if ever, in the lime light.

UltraSane•2 days ago

Java is still very popular and even being used for new projects.

Borborygymus•2 days ago

Java is swell and all, but having seen how the vendor treats even their large customers, I could never in good conscience recommend them to anyone I do business with. Better to miss out on the latest features and work with more respectful vendors IMO.

speed_spread•2 days ago

What vendor? OpenJDK is free and libre. If you mean Oracle, then that's a choice your employer made and yeah, you're SoL, especially for working in such a place.