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." mail.openjdk.org/pipermail/ambe… #JavaNext

java: RT @nipafx: 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. 🧵

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

Four highlights of #JavaNext twitter.com/nipafx/status/…

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: youtube.com/watch?v=dX8vF4… Here are four highlights. 👇🏾🧵

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: slides.nipafx.dev/java-next/2023…

I had a lot of fun in Hamburg last week - talking about #JavaNext at @jughh (slides: slides.nipafx.dev/java-next/2022…), but also just spending time in the city for a few days. So much to see!

Learned a ton about Java these last two days at #JBCNConf? Top it off now in room 111 and let me tell you about #JavaNext: How projects Amber and Valhalla, Panama and Loom are about to change Java forever.

On holiday on Crete right now, right there at the beach! 🏝️ But it wouldn't be a real journey without a visit to the local Java community, so I'll be talking at @devstaff_gr about #JavaNext in a few hours! meetup.com/devstaff/event… Meet you there?

Presenting #JavaNext at #jPrime (slides: slides.nipafx.dev/java-next/2022…), 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!

Looking forward to talking about #JavaNext at #DevoxxUK in 2h, but also sad that I won't get to see @heathriel's talk: How to Close the Diversity Gap (or, How Not to Perpetuate Bro Culture in Tech) devoxx.co.uk/talk/?id=4714 I don't have a choice, but you do - choose wisely! 😉

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: github.com/nipafx/demo-ja…

Hatte sehr viel Spaß bei @jugka zu Gast bei @DisyNet über #JavaNext vorzutragen. Hier sind die Folien, auch zu Amber und Panama, die wir aus Zeitgründen auslassen mussten: slides.nipafx.dev/java-next/2022…

Java Next, à quoi vous attendre de Java dans les prochaines années ? Un sujet très bien traité par Nicolai Parlog @nipafx. #java #javanext #salondevoxx #conférence #devoxxfr #takima

In 15 minutes I'll talk about #JavaNext at #DevoxxFR (room 243). All about projects Loom, Valhalla, Panama, and Amber. If you want to know what 1_000_000 threads, value types, or string interpolation could look like in Java, you don't want to miss this. 😋 See you there!

April will be busy: * talking about #JavaNext today at @jug_stuttgart, later at @DevoxxFR and @jugka * squeezed in two #JUnitPioneer streams * looking forward to modularizing @EclipseCollect with @TheDonRaab and @sirishapratha See you at the events or on Twitch! 😃

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

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` youtube.com/watch?v=a8OdwU…

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

In 30 minutes, I'll be on stage at #JavaZone to update a code base to Java after eleven. (Or will I? 🎃) Slides: slides.nipafx.dev/java-after-eig… Code base: github.com/nipafx/java-af… If you have any questions, ask here or use #JavaNext.