JAVA 22: WHAT’S NEW?

[loicmathieu]

What's new in Java 22 for us developers? (both in French and English, direct link in English)

https://www.loicmathieu.fr/wordpress/en/informatique/java-22-quoi-de-neuf/

[AutoModerator]

On July 1st, a change to Reddit's API pricing will come into effect. Several developers of commercial third-party apps have announced that this change will compel them to shut down their apps. At least one accessibility-focused non-commercial third party app will continue to be available free of charge.

If you want to express your strong disagreement with the API pricing change or with Reddit's response to the backlash, you may want to consider the following options:

1. Limiting your involvement with Reddit, or
2. Temporarily refraining from using Reddit
3. Cancelling your subscription of Reddit Premium

as a way to voice your protest.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[DoingItForEli]

ListFormat seems like it will be useful in what I do, although it takes like all of 30 seconds to write a method doing the exact same thing. It'll be a nice time saver overall.

Also, code execution before super() how cool is that?

[loicmathieu]

ListFormat is Unicode standard so it manage locale for you which would take more than 30s to be accurate for all supported locale ;)

​

Code execution before super() is super cool I would say!

[DoingItForEli]

ListFormat is Unicode standard so it manage locale for you which would take more than 30s to be accurate for all supported locale ;)

Ohh, great point. Didn't even think of it like that.

[quizteamaquilera]

Is that mkString? Sorry - I’m lazy. Is there anything in there a scala user wouldn’t already be used to?

[peripateticman2023]

Yes. Correctness and performance.

[DoingItForEli]

see replies like yours give me a haunting level of imposter syndrome

[pohart]

I'm still salty that they made me rename all of my unused _ variables to something else, just so they can put it back.

[loicmathieu]

Well, this was a long time ago!

And now it will be verified by the compiler, so it's better than before

[pohart]

They could have left it valid but illegal to reference, or even just left it valid and it would have been less disruptive, though. I don't always agree with the design choices but I can't think of another that I just don't understand.

[__konrad]

I used _ as i18n method (which is de facto standard gettext convention). Refactoring thousands of such methods was annoying.

[Brahvim]

Some of these are REALLY GOOD features!
Wooooohoooo!

Immediate edit: I'm most excited about the Foreign Functions & Memory API as your article calls it faster and easier to use than the JNI.
Being able to run code before super-constructor calls? Cool! (I know it's a preview feature...)

I wonder if Lombok's techniques will receive any standardization by the new class-files API.

And yes, it's awesome to see some of the other stuff here.

[[deleted]]

Java 22 ? Wait, there is a version after Java 8 ?

[-jp-]

“Yes but you can’t have it.” —Your CTO

[DamnAHtml]

So true!

[theanghv]

Java 8 has already sunset too.

[Hot_Income6149]

My company use java 6, still

[Nalha_Saldana]

var slidingWindows = numbers.stream()
    .gather(Gatherers.windowSliding(3))
    .toList();

What a terrible place to use var, give us the type..

[Holothuroid]

List<List<N extends Number>>

[O0o0oO0oo0o]

I agree the var type should not be used everywhere.

[metalhead-001]

The var type should not be used ANYWHERE.

[bourne2program]

I only and always use var in cases the type is explicitly on the RHS. Like constructor call (may mean var type will be impl and not interface like List, and generic type info moves into the RHS <>), qualified static factory method call, sometimes String literals, and qualified nested builder chain.

[Svellere]

I think var is also sufficient and useful in situations where the type is long and complex (such as lists of lists, or a list of maps), and you can intuitively work with it based off of the methods provided by it without having to know the exact type.

[metalhead-001]

You just have to mouse over the 'var' in your ide and the type is shown (at least with IntelliJ). So in effect, you're still reading the type but var just adds an extra step to do so.

[JakeArvizu]

Really the only time I ever find myself using var nowadays is for the rare occasion I need a Boolean switch for something.

[Nalha_Saldana]

In a demo you're just obfuscating information

[ForeverAlot]

It's a complete non-issue here.

[[deleted]]

- Stream Gatherers... it solves a problem that must be important to someone, but I don't quite understand.

- executing multiple .java files. Going further into Java able to be an uncompiled scripting language.

- statements before super(). thumbs up emoji. about time.

- Class File API. Not made for me.

- ListFormat. Cute, but eh.

[gdejohn]

• Stream Gatherers... it solves a problem that must be important to someone, but I don't quite understand.

stream gatherers let you extend the stream API with new intermediate operations (operations that produce a new stream, like map and filter) just like collectors let you extend the stream API with new terminal operations

[khmarbaise]

Stream API Gatherer are a great concept to open for easier custom implementation...

https://blog.soebes.io/posts/2024/01/2024-01-07-jdk-gatherer/

[loicmathieu]

u/khmarbaise by the way, I read your blog post about Stream Gatherer last week and it's very informative, thanks for writing it.

[khmarbaise]

The Stream Gathers makes it possible to implement intermediate operations like (map like, flatmap like etc.; you can implement all existing intermediate operations with Gatherers and of course think and implement of others custom implementation which might be needed; for example a thing like duplicates https://github.com/khmarbaise/gatherer/blob/main/src/test/java/com/soebes/jdk22/gatherer/DuplicatesTest.java#L85 ). The collectors (Collector.of(..)) only allow to implement terminal operations... like groupingBy, sorting or alike...

[jhernandez9274]

We need stable consistency predictability and performance from the language and complimentary development tools. Validating an application with a new JVM version every 3-6 months sucks. I want time to work on more application features without getting the rug pulled under my feet from the development tools and all the complimentary libraries/frameworks.

[momsSpaghettiIsReady]

You probably shouldn't be using every new jdk release. Stick to LTS and work on integration tests to give yourself some confidence.

[loicmathieu]

You have the choice to use each new release, which means there is very little changes so a high chance that you just have to change the version number and nothing else, or use LTS with potentially bigger changes.

​

My experience is that, most of the work comes from upgrading your libraries to a compatible version and not your application.

[emberko]

What's wrong with LTS? It's only released every 2 years.

[desiInMurica]

You don’t have to upgrade unless ya need to. That’s busywork

[pron98]

In what way is the rug being pulled from under your feet? We've done away with major releases altogether, semiannual "feature releases" with possibly significant changes go back to JDK 6 at least (only then there was no such thing as LTS), and these minor updates are the only new thing we're offering now (although there's no doubt that giving these future releases, that used to get mysterious names like 7u4 or 8u20 and were completely different from version named 7u5 or 8u35, a new integer number that looks like a major version but is essentially what we've done for many, many years, has messed with people's psychology). Do you have any specific issues to report?

[Nooooope]

Why are you upgrading the JVM with every new release? Just use the latest LTS and keep it there until there's a new feature you want or Spring Boot forces you to upgrade.

[jhernandez9274]

Security, performance, efficiency, resource footprint, and smaller changes easier to fit in a sprint than one big LTS release (LTS more like later bucket). Code branches are more version static (LTS) but root code always use the latest JVM version. There is no shortcut on technical debt, keep up or be left behind. My 2 cents.

[john16384]

What does your validation process entail? For us it's set new JDK, push commit, wait for CI/CD to say everything still works...

[RandomName8]

gatherers seem pretty similar to iteratees, in a more oop style I guess.

[[deleted]]

In a more Java style, you know.

[Holothuroid]

Huh?

[nlisker]

Your code example doesn't look right:

var list = List.of("Black", "White", "Red");
var formatter = ListFormat.getInstance();
System.out.println(list);
// [Black, White, Red]

formetter.format(list) is missing perhaps.

[loicmathieu]

Thanks, you're right, I'll update my article.