"I think Loom is going to kill reactive programming." ~Brian Goetz

Hi,

“I think Loom is going to kill reactive programming.”

This statement comes from Brian Goetz .

Do you know who he is? Brian has been the Java Language Architect at Oracle for 13 years.

He is the author of “Java Concurrency in Practice” - a standard work for every Java developer .

He was also the one who brought JSR-335 - Lambda Expressions - into the language.

What Brian says has substance. You’ll hardly find anyone else in the world who can provide a better outlook on the future of Java and its ecosystem.

The interview is already a year old. I stumbled upon it by chance this week. And this statement stuck with me. Because it confirms what I’ve been discussing with colleagues for a year. I believe Project Loom will fundamentally change the way we develop. I also described this in this blog .

Last week, I wrote in a newsletter that no one writes about Project Loom .

And then I come across this interview.

I began to doubt myself a little. Am I the fool here who overestimates the impact? Am I the only one hyped about the feature?

But apparently, this is the case currently. The entire Java world is keeping quiet. Hardly anyone talks about the consequences of Project Loom.

At least until now. And in my bubble. Let’s see what the topics at the conferences in the fall are. In November, I’m giving a talk at W-JAX . There, I should be able to tell whether Project Loom is a thing or not.

I’m excited.

Rule the Backend,

~ Marcus