Java is back in action, with Java 21

With all the noise about #VirtualThread in #Java21 as the big thing, I had a feeling I had seen this somewhere before. Its that feeling of “I have seen you before”, if you understand it.

So, after looking for all the keywords I could think of, finally, I did find it.

I have programmed in Java for over 26 years, starting 1997, until recently. Mocsh ( My Personal Finance Email reader ) was implemented in Java, and maintained, until as late as 2019.

Then, when I started consulting, I was introduced to NodeJS. It was the platform for “scalable” applications because of its “async” programming model. And I must appreciate that it makes it easy. In my opinion, too easy. And that results in the programmers not realising the actual impact of the keyword.

#kotlin came with its coroutings. Helped make async programming on the JVM easier. #Java did bring the Future construct, but it just did not fit the programming philosophy of the language. I could never make the transition to Kotlin. If I had to learn a new language, JS+NodeJS was already established at the future.

I was sad to leave Java. But I had no choice.

I have been watching the language have a near death experience, with #Java8 . But starting #Java9, with the 6 monthly cadence, things have been moving at a significant pace. And I am loving watching the progress.

I did not have confidence to “commit” until I saw #Java17. Then I watched closer, and with #Java21 , I believe, that Java is back in a place where it should be taken seriously by all. Specially with the #VirtualThread project.

When I saw that, I was ecstatic. Green threads are back in fashion. I have seen the “m:n” thread ratio in Java during the early years. And was very unhappy when it was taken away.

With this, the #AsynchronousProgramming / #ReactiveProgramming has been implemented in an elegant way in Java.

I am warming up to Java. What about you ?

More read: https://en.wikipedia.org/wiki/Green_thread