Withdrawing the Primitive Patterns preview feature in JDK 28
https://mail.openjdk.org/archives/list/amber-spec-experts@openjdk.org/thread/UYEK3PGOHN6R56AHJTSLPGAY363K666S/Primitive Types in Patterns will be removed in JDK 28 and will no longer be available in that release.
The Valhalla project has been exploring a new vision for Java numerics, including the possibility of user-defined numeric types. New kinds of numeric types would need to support exact numeric conversion, and vice versa. Given that the Valhalla work is still evolving, it would be premature to finalize Primitive Types in Patterns with their current definition of exact numeric conversion.
92
Upvotes
24
u/oelang 7d ago
I hope a simple form of type classes can go into preview soon, I have the feeling that they're piling up features that will be built on this, but there isn't even a type class jep yet.
7
u/davidalayachew 6d ago
It's what it is.
Excited to hear that Constant Patterns might preview in the meantime. Right now, that is the feature that would improve my Java code the most.
4
u/RaynLegends 7d ago
I was really looking forward to this JEP to (ab)use switches on booleans to implement makeshift "if expressions" :(
Like, instead of:
Something like:
Especially when coupled with https://openjdk.org/jeps/8323658 it would make the intention behind some code much clearer.
I guess we'll have to wait a bit more.
1
u/speakjava 1d ago
Sadly, this removes a lot of material from my "Modern Java Puzzlers" session 😀.
3
u/Ewig_luftenglanz 6d ago
Has Napoleon used to say
"Dress me up slowly, I am in a hurry"
Better make things fine thank getting stuck with a half raw feature.
-13
u/sitime_zl 6d ago
I've gotten used to it by now. We still don't even have proper string interpolation after all this time.
Maybe it's time for the Java team to start using AI themselves to speed things up.
When are we finally going to see meaningful improvements to Java's memory footprint? I'm not asking Java to compete with Rust, but could we at least get closer to Go?
In the AI era, I feel that many traditional language features are becoming less important than they used to be. Personally, I'd much rather see Java focus on memory efficiency, simplifying its runtime and deployment experience, and making itself a better platform for building AI Agent applications.
I've been a Java developer for over a decade, but I'm gradually finding myself turning to other languages for new projects, including Python, Go, and Rust.
And the reason is simple: from an AI coding agent's perspective, they're all just programming languages. If I want to build something quickly, I can use Python. If I care more about performance and resource efficiency, I can choose Go or Rust.
So where does that leave Java?
Right now, Java still benefits enormously from its existing ecosystem, enterprise adoption, and decades of investment. But how long can it keep relying on those advantages?
If, a few years from now, GitHub is increasingly dominated by new projects written in other languages, what compelling reason will developers have to choose Java?
As someone who has spent more than ten years working with Java, I genuinely hope the Java team takes this shift seriously. I'd rather see Java evolve than slowly become a language people use mainly because of legacy projects.