Java 12 is here.

Why so many releases now.

It was good earlier, years taken for next release.

Atleast we could update our resumes properly.

I am still using Java 8 because I don't need that stupid module System.

@EaZyCode Java 9 modules.

They started agile development.

@EaZyCode if you don't need it then don't use it. You can use Java 12 without using modules.

I think I read somewhere that they changed it to a half year cycle to make new features available faster. Previously you had to wait for years.

Their new approach is a pain, they should have at least make it every year or so and not every 6 months

Ther@gitpush agree. Doesnt make sense

@hac@SHA-16384 Haha. Typical recruiters.

@SHA-16384 You forgot
4+ years in Flutter
15+ years in Android development
16+ years in iOS development
and not older than 22 yrs old

Earlier the java versions were like GDP of Nepal, Very small and constant.

Now, they are like prime minister of Nepal, They change too often and we can't even tell which one is the latest.

I actually prefer the new release cycle. If we were on the old one, we'd be waiting another year to get a new version with half the new additions of 9-12.

I'm all for quick release cycles, but the Java 12 feature set seems utterly pointless.

The only language change is to do with switch expressions - and even that's a "preview" feature. That's it. No raw string literals. No new APIs. Nothing else whatsoever.

Shenendoah is the only potential saving grace. But again, that's experimental, so beyond a few hard core devs, most people will neither know nor care about it. Beyond that, there's some minor tweaks to G1, and that's a wrap. All the other features are JVM or internal JDK build stuff, not to do with Java itself.

It definitely feels like releasing just for the sake of releasing...

May I interest you in some Kotlin?

To me it feels like they implemented all what kotlin had into Java fast and now just pushing more from other places.

@ilikeglue That is what competition results in, yes.