Java Next - From Amber to Loom, from Panama to Valhalla by Nicolai Parlog

Java's four big projects are entering the home stretch: Amber and Panama have already incubated, previewed, and even finalized some features, Loom and Valhalla are on track to follow soon. Time to take a closer look at how...

- Project Amber makes the language more expressive and ready for today's and tomorrow's problems
- Project Panama cuts through the isthmus separating Java from native code
- Project Loom enables hassle-free and efficient structured concurrency
- Project Valhalla mends the rift in Java's type system and improves performance

After this talk, you will know what to expect from Java in the next few years.

[MichaBerger]

I think that as these big projects accumulate, there is indication there are problems that the Java community would be well served by a successor language, rather than shoehorning in features while hampered by backward compatibility. Even Kotlin was started too early to smoothly capture a number of these great ideas.

Alternatively, Java 20 would have been Java 1.20 in the old naming scheme, maybe we should be talking about Java 2.0...

(Donning my asbestos suit now. This is a matter of taste, not objecive correctness, and peoples' tastes always differ.)