What’s New Between Java 11 and Java 17? (2021)

#1

Post by ptrik » Wed, Mar 30, 2022, 2:30 AM UTC

What’s New Between Java 11 and Java 17? (2021)
mydeveloperplanet.com

Re: What’s New Between Java 11 and Java 17? (2021)

#2

Post by ibiza » Wed, Mar 30, 2022, 4:06 AM UTC

Conveniences. Will Valhalla or Loom ever drop?

Re: What’s New Between Java 11 and Java 17? (2021)

#3

Post by fulafel » Wed, Mar 30, 2022, 4:15 AM UTC

It would be interesting to see qualitative surveys of new Java code that appears eg on Github that would give information about whether the real-world practice in Java is converging toward expressivity of higher level languages and reduced incidental complexity.

Re: What’s New Between Java 11 and Java 17? (2021)

#4

Post by scubbo » Wed, Mar 30, 2022, 4:28 AM UTC

Some great features here! Looking forward to when my team upgrades to Java 17 in 2035!

Re: What’s New Between Java 11 and Java 17? (2021)

#5

Post by [deleted] » Wed, Mar 30, 2022, 4:28 AM UTC

[deleted]

Re: What’s New Between Java 11 and Java 17? (2021)

#6

Post by lolive » Wed, Mar 30, 2022, 4:29 AM UTC

ibiza wrote: post #2

Conveniences. Will Valhalla or Loom ever drop?

Exactly the question I asked myself ;)

Re: What’s New Between Java 11 and Java 17? (2021)

#7

Post by adgjlsfhk1 » Wed, Mar 30, 2022, 4:30 AM UTC

ibiza wrote: post #2

Conveniences. Will Valhalla or Loom ever drop?

My guess is 2 years before Fortran gets generics.

Re: What’s New Between Java 11 and Java 17? (2021)

#8

Post by jpgvm » Wed, Mar 30, 2022, 4:44 AM UTC

ibiza wrote: post #2

Conveniences. Will Valhalla or Loom ever drop?

They will, getting closer all the time. I don't think before ~Java 21 but I think that isn't an unreasonable time frame considering how big they are.

Re: What’s New Between Java 11 and Java 17? (2021)

#9

Post by oaiey » Wed, Mar 30, 2022, 4:45 AM UTC

It looks like C# and Java are now developed in parallel with the same features.

Re: What’s New Between Java 11 and Java 17? (2021)

#10

Post by jicea » Wed, Mar 30, 2022, 4:50 AM UTC

I’m a backend developper, working on medium to big Spring Boot apps. Two years ago, we introduced Kotlin in our code base with really good results on code quality.

With Java 17, the gap is narrowing between Kotlin and Java. Kotlin has still unique features that I love (extension methods for instance), but the big one is nullability. You can use @Nullable/@NotNull annotations in Java but I largely prefer having nullability backed in types with Kotlin. Some people say nullability is not a problem: with 30 developers of various quality, I can ensure it is a problem. I don’t see Java addressing nullability in a better way in the near future, so I’m going to stick with Kotlin.