Java 8, 9, and 10 roadmap

I found the topics on streams and internalisation vs. collections and externalisation to be quite fascinating. The more I look at this particular problem the more that I wonder that it’s still maybe too low level - still describing a lot of “how do to something” rather than “what I wanted it to do”. But a great step in the right direction.

Possibly the ultimate evolution would be to embed SQL properly into Java code - using real SQL syntax rather than all this lambda business with its funny brackets and dashes and arrows and so on - and let some magic under the covers actually work out what it is you are trying to do. I dunno. Things just keep evolving from underneath me. I should have stuck with BASIC.

Cas :slight_smile:

To put it rather blunt: multi-line strings would be enough. Compile-time safety on SQL is nice but I’m confident it will always be a mess as Java code.

The nice thing is that we’ll see a huge revamp in the JDK libraries that all JVM languages will benefit from. The Java syntax will not be of much importance. After JDK7 and InDy the Java language itself has been made kinda obsolete if you ask me. What will be very interesting to see is what kind of magic will be possible using Scala, Kotlin or even Javascript (the Nashorn engine will be in JDK8).

@Riven Hm yes that’s true. Though when I was a Powerbuilder jockey the simple integration of SQL directly into the language was… simple.

@Spasi Java++ :smiley: Like Java, with blackjack, and hookers!

Cas :slight_smile:

I’m interested.

The merger of the JRockit & HotSpot teams + VMs is very cool. OK. That’s old news I suppose.

WRT: Pure OO comment. I think I see some of the brush-strokes. Some of the invokedynamic examples are accessing “int.class, float.class”, etc. So the internal primitive classes are getting some methods at least for use in other languages. Also it looks like tagged-unions (a la LISP/SmallTalk) are going to be added HotSpot: (text here)