Live data from Hacker News

JDK 9 release schedule

mail.openjdk.java.net

21–30 of 161 posts

Re: JDK 9 release schedule

#21
post #5
post #3

Does anyone have the full changelog of added/new features.

Here is the list: http://openjdk.java.net/projects/jdk9/

Does anyone have a list of smaller gems that are not on that list? For example JDK 9 contains an implementation of the CRC32C-algorithm which can be used by web developers to create compact entity tags. I read somewhere that there is even hardware support for it but I'm unsure whether it's being utilized by the JRE.

See http://download.java.net/java/jdk9/docs/api/java/util/zip/CR....

Re: JDK 9 release schedule

#22

So, uh, how many people are using Java 8? I still see projects using Java 5...

> I still see projects using Java 5...

Are you serious? Even the worst shops I've been at have at least moved their JVMs to Java7 back around 2014. I mean you can take all your existing JARs from Java4 and run them on Java8 and nothing should break. Recompiling them might be another issue, but still not a huge one.

Re: JDK 9 release schedule

#23
post #12

So, uh, how many people are using Java 8? I still see projects using Java 5...

The annoying thing is that Java 8 is the only currently supported version of the language. The glacial development speed somehow still manages to deprecate versions faster than they fall out of use.

While Java 8 is the only version that is freely supported from Oracle, it is still possible to buy commercial support for older versions of Oracle's Java platform.

The speed at which they stop freely supporting older versions feels much like a way to squeeze big, slow moving organizations for support contracts.

Re: JDK 9 release schedule

#24
post #21
post #5

Earlier quoted context omitted.

Here is the list: http://openjdk.java.net/projects/jdk9/

Does anyone have a list of smaller gems that are not on that list? For example JDK 9 contains an implementation of the CRC32C-algorithm which can be used by web developers to create compact entity tags. I read somewhere that there is even hardware support for it but I'm unsure whether it's being utilized by the JRE. See http://download.java.net/java/jdk9/docs/api/java/util/zip/CR... .

I guess you need to go through JEP list and check all marked for 9 either "F Com 9", "F Clo 9".

The proposed ones "F Pro 9" might just make it on 10.

http://openjdk.java.net/jeps/0

Re: JDK 9 release schedule

#25

So, uh, how many people are using Java 8? I still see projects using Java 5...

The vast majority of projects, at my employer. I personally upgraded several hundred JVMs running several dozen services - upgrading was simple and almost entirely painless.

In addition to benefiting from the new features, being up-to-date is good for recruiting. You tell someone they'll be working with Java 6 and (in the absence of other evidence) they'll assume it's a legacy product suffering from chronic under-investment. Not exactly the impression you want to give job seekers!

Re: JDK 9 release schedule

#26
post #5
post #3

Does anyone have the full changelog of added/new features.

Here is the list: http://openjdk.java.net/projects/jdk9/

Am I missing properties? Dear god it's 2016, with Java8, and we still don't have real, language-defined properties? I mean you can use Lombok (and if you're not, you should be!), but that's something that really need to be built into the language. C# has them, Python has them, Ruby has them .. even other JVM languages like Scala have them!

I'm really glad I get to do Scala development full time. Even with all the recent improvements to Java 8, I feel the future of Java isn't the language, but the JVM and all the other languages that run on top of it (Scala, Groovy, Clojure, JRuby, etc.)

Re: JDK 9 release schedule

#27

So, uh, how many people are using Java 8? I still see projects using Java 5...

> I still see projects using Java 5... Are you serious? Even the worst shops I've been at have at least moved their JVMs to Java7 back around 2014. I mean you can take all your existing JARs from Java4 and run them on Java8 and nothing should break. Recompiling them might be another issue, but still not a huge one.

Yes, the problem is when you as a developer have zero value for the company IT and have to make the application run on the servers that IT configured for the whole enterprise, not just our snowflake application.

Re: JDK 9 release schedule

#28
post #23
post #12

Earlier quoted context omitted.

The annoying thing is that Java 8 is the only currently supported version of the language. The glacial development speed somehow still manages to deprecate versions faster than they fall out of use.

While Java 8 is the only version that is freely supported from Oracle, it is still possible to buy commercial support for older versions of Oracle's Java platform. The speed at which they stop freely supporting older versions feels much like a way to squeeze big, slow moving organizations for support contracts.

I appreciate that, even with this "fast" pace I still need to target Java 7, and I am aware of projects in even older versions.

Re: JDK 9 release schedule

#29

So, uh, how many people are using Java 8? I still see projects using Java 5...

The vast majority of projects, at my employer. I personally upgraded several hundred JVMs running several dozen services - upgrading was simple and almost entirely painless. In addition to benefiting from the new features, being up-to-date is good for recruiting. You tell someone they'll be working with Java 6 and (in the absence of other evidence) they'll assume it's a legacy product suffering from chronic under-inv…

> they'll assume it's a legacy product suffering from chronic under-investment.

Or Android.

Re: JDK 9 release schedule

#30

So, uh, how many people are using Java 8? I still see projects using Java 5...

> I still see projects using Java 5... Are you serious? Even the worst shops I've been at have at least moved their JVMs to Java7 back around 2014. I mean you can take all your existing JARs from Java4 and run them on Java8 and nothing should break. Recompiling them might be another issue, but still not a huge one.

Earlier this year I was working with an outfit that was on Java 4 for A Really Important Business Application. That said, they were looking at moving to IIRC 7 just as I was leaving.
Post reply on HN