You can easily bundle the JVM with your application so that you can run on your JVM, guaranteed. You would no longer need to depend or expect a user to be capable of installing a system-wide JVM (that could be a different version, etc).

It does not mean abandoning the JVM as a concept, just giving you more control over how you invoke the JVM to run your application.

That seems to be the direction that they are headed in. Alot of the slides show "classpath" crossed out. Breaking up packages into separate & versioned bundles. So I'd assume that a JRE just becomes a collection of all the various versions.

I wish they'd just ditch the whole idea of a system JVM, forever, and concentrate on making Java available as an embeddable library.

Cas

Yes! And support iPhone runtime and Google NaCl.

I love the JVM alt-language space, the libraries, the IDEs, the build tools, and the fast runtime performance (faster than almost everything except C/C++). Those pieces are what keep me excited about JVM. I don't think I'd build another serious project in plain Java; I'd rather use Scala or maybe Kotlin.

And I'm also getting the impression that things are moving a little faster now than in the recent past.

If by "the recent past" you mean the last 5 years that won't be too difficult

Even crawling along at a snail's pace is better than a complete standstill (except for some bug fix / security hole fix AKA applet break releases)

Still I see the platform diversify even more. More languages than you can shake a stick at, and more are coming. I used to like diversity and freedom, but in today's world it is actually a big hindrance IMO; people don't seem to think like that anymore.

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.

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).

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)

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org