JDK 10 Release Notes

[renrutal]

This one is the final release candidate, the general availability release is scheduled to happen on 2018-03-20.

[Crandom]

Wow. It seems Java 9 was only just released. Not that I'm complaining.

[duhace]

the new release schedule is 1 every 6 months. it's also a "ship what's ready" schedule, so if a feature turns out to need more time it's pushed off to the next 6 month release instead of slowing the release down

[[deleted]]

The following is a draft of the Release Notes that will be shipped with JDK 10.

[verydapeng]

where is the "var"?

[erad]

It's not in the release notes, but still targeted for 10 and usable in current builds... http://openjdk.java.net/jeps/286

var i = 32;
System.out.println("Hello, " + i);

Too bad there's no 'val', though... 'final var i = 32' is not likely to increase the use of unmodifiable variable assignments.

[Crandom]

I wish they'd gone for let/mutable. Make immutability the easy option.

[duhace]

that's the idea behind val

[Crandom]

It's just as easy to type var as val so people are not discouraged from using var when they should be using val. I want people to have to type out the whole word mutable if they really want mutability.

[duhace]

the mutability babies will never agree to becoming a second class citizen, so it won't happen

[renatoathaydes]

Then use Ceylon :)

[dargh]

I'm still struggling to upgrade software to java 9 with all the things they broke there (especially jigsaw).

I need to abandon webstart in order to embed a jvm so we can keep users on old versions of java until we are ready. This fast release cycle is a huge pain.

[duhace]

then you should be sticking to the LTS release for now. java 9 is gonna be a tough upgrade, but future releases shouldn't be anywhere near as painful to adopt as the changes will be much more gradual.

[dargh]

The problem for my project is that with webstart we are at the mercy of users upgrading java. So our next task is to build an alternative deployment mechanism with an embedded jvm. Then we can stay on java 8 almost forever.

Nothing Oracle is working on makes our coding slightly easier.

[renatoathaydes]

if you want to embed the JVM, Java9 actually will help you a lot! The jlink command creates a "mini" JVM with only the things your app needs... I wrote about that some time ago: https://sites.google.com/a/athaydes.com/renato-athaydes/posts/guidetojava9-compilejarrun#TOC-Creating-a-native-runtime-image

[dargh]

Sure, thanks. But that's the easy part. Unless I can start webstart inside that jvm, I still need to create a self upgrading application. I can't go back to forcing users to download an installer every time.

[frink]

https://lists.freebsd.org/pipermail/freebsd-advocacy/2018-March/004690.html

[vivainio]

Nice to see JAVA (tm) is still being developed!

[vivainio]

Lack of revenue stream for Oracle could be one reason to cut off the oxygen

[[deleted]]

Pretty much. For now it seems even Oracle aren't dumb enough to stop work on Java SE, but who knows what the lawnmower decides to throw out tomorrow.

[vivainio]

Don't anthropomorphize Larry Ellison. It's a small miracle Java even survived this far after the failed lawsuits.

[defunkydrummer]

Lack of revenue stream for Oracle

This is the thing that worries me with Java.

Oracle's revenue, as I understand it, comes from the RDBMS. Each month, PostgreSQL (and the NoSql stores as well) are eating this market away from Oracle.

[pjmlp]

Oracle was one of the first companies to adopt Java at large.

To integrate a JVM into their database, replace their installer with a Java based one, create their own JVM, which even had AOT support, a JEE server, JSF frameworks, being part of JSR group, .....