JDK 9 release schedule • Hacker News Board

Re: JDK 9 release schedule

#11

Post by javanese » Tue, Oct 18, 2016, 6:20 PM UTC

So, uh, how many people are using Java 8?

I still see projects using Java 5...

Re: JDK 9 release schedule

#12

Post by ygra » Tue, Oct 18, 2016, 6:21 PM UTC

javanese wrote: post #11

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.

Re: JDK 9 release schedule

#13

Post by theandrewbailey » Tue, Oct 18, 2016, 6:28 PM UTC

javanese wrote: post #11

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

I am. Granted, it's only the blog hosted from my basement.

Re: JDK 9 release schedule

#14

Post by brianwawok » Tue, Oct 18, 2016, 6:29 PM UTC

javanese wrote: post #11

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

Most not totally old projects are on JDK8. Don't look at some crufty apache product, but look at medium size business apps... those have all been JDK8 for a while now.

Re: JDK 9 release schedule

#15

Post by erl » Tue, Oct 18, 2016, 6:30 PM UTC

geodel wrote: post #5

gravypod wrote: post #3

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

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

I appreciate changes that make it easier to monitor and debug applications. Looking forward to some small goodies that I haven't heard much about before:

http://openjdk.java.net/jeps/228 - Add More Diagnostic Commands. For example more insight into JIT:ed methods and the code cache.

http://openjdk.java.net/jeps/158 - Unified JVM Logging. Logging from the JVM, e.g. GC logging and classloader logging, are configured and printed uniformly.

http://openjdk.java.net/jeps/259 - Stack-Walking API. Efficient API for walking the current call stack.

Re: JDK 9 release schedule

#16

Post by jwn » Tue, Oct 18, 2016, 6:31 PM UTC

merb wrote: post #8

jwn wrote: post #4

Earlier quoted context omitted.

Looking at http://openjdk.java.net/projects/valhalla/ , I don't see a whole lot of value compared to JDK9. What's your basis for wanting 10 so badly?

well as others already pointed out, value types. this changes the way how the JVM uses Memory in certain ways and might be a huge improvement for a lot of stuff. specialized generics. this is a huge one, too, less boxing is always a win. JEP-286 less typing. Maybe Project Panama and maybe a even better AOT. Compared to what JDK 9 brings, this is huge. JDK 9 brings a Module system which was already possible (and a lot…

Good answer, thanks =) My question earlier was an honest question, asked out of curiosity...

Re: JDK 9 release schedule

#17

Post by jdmichal » Tue, Oct 18, 2016, 6:39 PM UTC

whateveracct wrote: post #9

papercrane wrote: post #7

Earlier quoted context omitted.

I'm pretty excited about that one, it's JEP-286, http://openjdk.java.net/jeps/286 . Valhalla is pretty big. Goetz described it as pulling on a very long string. It's going to touch everything in the JVM, including reifing generics, although as I understand it, erasure of Objects may be here to stay for the language.

Erased generics will surely stay and are a good thing. If they were removed, Scala would be in trouble (or rather, scalac would have to perform erasure itself, which in turn would mean that interop from Java wouldn't be good anymore). What's broken in the JVM isn't erased generics but instead runtime reflection that is a lie due to erasure. Type erasure though is definitely an example of Java getting something very r…

Are you attempting to separate the concepts of specialization vs reified generics? Java does neither right now, and both effects are due to type erasure -- the runtime simply doesn't have the necessary information. I'm not quite sure where you're trying to draw the line.

Furthermore, runtime specialization (as opposed to compile-time) would seem to require reified types. So that further confuses things. But you can definitely have reified types without specialization, which I think is the point that you are trying to convey.

Re: JDK 9 release schedule

#18

Post by duaneb » Tue, Oct 18, 2016, 6:42 PM UTC

brianwawok wrote: post #14

javanese wrote: post #11

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

Most not totally old projects are on JDK8. Don't look at some crufty apache product, but look at medium size business apps... those have all been JDK8 for a while now.

> Don't look at some crufty apache product, but look at medium size business apps...

What do you think those medium sized business apps are built off of if not things with JVM dependencies? It's not so simple.

Re: JDK 9 release schedule

#19

Post by bitmapbrother » Tue, Oct 18, 2016, 6:44 PM UTC

spullara wrote: post #10

The next interesting thing for the JVM is value types in Java 10. It may convince me to use it pre release.

I'd also add:

  Generic Specialization  
  Reified Generics  
  Native Function Calling
  Native Data Access
  New Data Layouts

Re: JDK 9 release schedule

#20

Post by pjmlp » Tue, Oct 18, 2016, 6:44 PM UTC

spullara wrote: post #10

The next interesting thing for the JVM is value types in Java 10. It may convince me to use it pre release.

There are Valhalla releases available, but I bet stable is something they are not.