Posts
How to enable Virtual Threads? During my talks about Java 19 (which have the mandatory part dedicated to Virtual Threads), I’ve been asked: how do I enable Virtual Threads in the JVM? quite a few times.
This question carries an assumption that there’s some kind of switch, which has to be activated or hit to “magically” turn good ol' Threads into Virtual Threads. AFAICT there is no such thing right now, and I rather doubt there will be one in the future.
Let’s be honest: we’ve been waiting for the Virtual Threads quite some time. We’ve been waiting eagerly, we’ve seen names changing (they’re not fibers folks), but here there finally are: Virtual Threads.
Some say the Project Loom is the biggest change Java has seen since version 8, lambdas, and streams. Some say it’s even bigger than that. Discussion aside, they are a huge change, it seems.
I remember how we were excited (I was still at the university back then), that we could finally use some real Threads in Java on Windows.
What do I think about Lombok?
I think it’s a nice island, and I wish to visit it one day.
What do I think about Project Lombok?
Well, I’ve been asked this question so many times, I’ve decided to write this post. Its main purpose is to be able to paste the link and back up, because the (yet another) discussion might be so intensive, that fists will be shaken and heads will roll… There are three assumptions here:
Many features and changes we see coming live in new Java version (if not most of them) are developed under so-called umbrella projects. We frequently see syntax improvements from project Amber, project Jigsaw is about bringing modules, project Loom (surprise, surprise) is about new threads, project Panama roughly speaking is about using native stuff safely and efficiently, and among the most known ones, project Valhalla starts to become a thing, thanks to JEP-390 being included in Java 16.
Last year I wrote two posts about torturing Java records with Lombok. Fortunately (or not, depends on your point of view), Lombok’s team decided to end these sick plays. However, we don’t give up and go for builder!
Last year I wrote two posts about torturing Java records with Lombok. Fortunately (or not, depends on your point of view), Lombok’s team decided to end these sick plays. However, we don’t give up and go for builder!
Many times during my talks covering Java records I was asked if the result of hashCode() of a record is cached. Let’s see ;-)
It seems “everyone knows” that “with records you don’t have to write equals() and hashCode()”. What if I told you this might not be always true…?
After using Linux for quite a few years now, I’ve accidentally embarrassed myself. I spend a lot of time using terminal in various forms. I’m not sure I know all Vim quirks (not to mention Emacs, but let’s not talk about this operating system now), therefore I was pretty confident I know how to use the terminal emulator… Today I’ve found a nice new feature, really low-hanging-fruit, so I’ve decided to share it with you, along with some other goodies (maybe not some obvious to Linux neophytes) I’m being asked about after my talks.
This post should have a nicer title, but I can’t find it. It’s about security factors and some misperception about them.
