While preparing my Deep Dive talk on Java 21 for friendly Java User Groups, I’ve noticed a curious case of JEP 443: Unnamed Patterns and Variables (Preview). I’ve managed to create a reproducer, so I’d like to share the findings here. I assembled a simple demo of the JEP. It’s obviously very nice and for sure it will improve Java’s abilities to shine in data-first coding scenarios. However, this JEP is not only about switch and ifs, it’s also about lambdas, catch blocks and so on.
Java™ 21 is real now. And so are virtual threads. Everyone got excited about them, yet you prefer to keep your Java 8 job forever, and you already have a nice plan to “accidentally” derail the migration to 21 by using virtual threads in a very, very unfortunate way. What a pity… So you decided to come for this talk to look for some inspiration ;-) Okay, please join us to learn how NOT to use virtual threads, and see the potential performance pitfalls of using them the wrong way.
Hey, there are two major Java versions released every year! We don’t have to wait 3 years or so for new features anymore. Isn’t that cool? 😉 Java was supposed “to be slow”. However, Java turns out to evolve so fast, that next releases aren’t just version bumps, but might significantly change the rules of the game. That’s a good reason to check out what’s new in Java. To name a few changes:
Let me start this entry with a dad joke. An electron rides a motorcycle. Suddenly, a police officer stops the electron and says: ‘I had to stop you, because you were speeding, driving exactly 178 and half kilometres per hour.’ ‘Well, THANK YOU VERY MUCH, officer!’ the electron says, ‘Now I have absolutely no idea where I am!!!’ Some dad jokes are terrible, and don’t worry if you don’t get this one.