#JavaNEXT

Java devs no longer need the visitor pattern! With sealed classes (final in #Java17) and pattern switches (preview in 17), #JavaNext offers a better and shorter solution to the problems the pattern addresses.

Once we have value types, we could replace mutable iterators with immutable cursors and get rid of for-each loop's garbage. Interesting exploration by John Rose: #JavaNext

Interesting detail on primitive types: "As a matter of style, we suggest avoiding the legacy wrapper class names in new code, preferring the .ref types instead." I.e. `int.ref` instead of `Integer` just like we'd do with custom primitives, e.g. `Point.ref`. #JavaNext

val html = ` <div> <p>OMG, I can't <b>believe</b> we get multi-line strings in #Java12!</p> </div>`.align(); #JavaNext

Presenting #JavaNext at #jPrime (slides: I asked "What's your newest Java version in prod?" Java 7: 1 (not the same guy as previous conferences - I asked) 8: 10% 11: 20% 17: 20% 18: 0 What about the other half? 🤷 But 40%-80% beyond 8 is very nice!

Learn everything about #JavaNext in my speedrun through projects Amber, Loom, Panama, and Valhalla at #JavaLand2022 in Wintergarten. In 3 minutes, so better hurry. 😉

Over the last weeks, I've back-filled and updated my Java X Feature Demo, all the way up to #Java18, including a bit of vector API image manipulation for #JavaNext - check it out:

How Java's upcoming string literals may manage indentation: #JavaNext

How do you name unused variables? If even just having to make that choice annoys you (it's not just me, right?), read on for how #JavaNext will fix that and make pattern matching (how's that related?!) more maintainable in the process. 🧵

Slides for today's #GeekOutEE talk "#JavaNext - New Releases, Valhalla, Amber, and More Goodies": By the way, Tallin's Creative Hub is an awesome venue, very steampunky. Some impressions...

Conversation with @BrianGoetz about pattern matching in #JavaNext: * why `Map::get` should be a pattern * the linear thinking trap * null handling in pattern matches * exhaustiveness in switch statements * the rehabilitation of `switch`

In 30 minutes, I'll be on stage at #JavaZone to update a code base to Java after eleven. (Or will I? 🎃) Slides: Code base: If you have any questions, ask here or use #JavaNext.

Sitting in the train to visit family over the weekend I'm watching the #JVMLS2019 talk on Project Loom by Alan Bateman and Rickard Bäckmann ( Wifi permitting, I will tweet my comments. 1/? #JavaNext

Last week I gave my updated #JavaNext talk at @VoxxedZurich - in 45 minutes, you get an overview of the current state of projects Amber, Panama, Valhalla, and Loom: Here are four highlights. 👇🏾🧵

#GeekOutEE just published videos of all talks. Kudos! If you have an hour to learn about how Java is evolved and which great things are coming, check out my talk #JavaNext: video: slides:

Wohoo, #ProjectValhalla started publishing early access builds: Will play with it on Friday. This is gonna be awesome!! #JavaNext

Had a great time talking about #JavaNext at @VoxxedZurich! For the parts that I had to skip (gimme 60 minutes, please! 😉), check out the slides:

[NEW POST] How to use #JavaNext preview features like switch expressions and text blocks: * command line flags * Eclipse, IntelliJ, Maven, Gradle configuration * safeguards * WHY?!

In a short interview with @InfoQ, @BrianGoetz comments on the proposal to allow hyphenated keywords in Java (e.g. `non-null` or `value-class`): The answer to `break-with` vs `yield` is interesting, too. #JavaNext

Big string template revamp - processors are out! 😳 "Processors were envisioned as a means to abstract the transformation of templates to their final form. However, Java already has a well established means of abstracting behavior: methods." #JavaNext