The Reactive Revolution • Josh Long • YOW! 2019

[@GOTO-]

We are currently releasing older YOW! videos to serve as a valuable archive, preserving historical content. It is possible that a video is perceived as outdated. We believe it offers insightful glimpses into the past, enriching our understanding of history and development.

[@Tony-dp1rl]

If you are using Java for reactive (or any asynchronous) programming you are essentially using a hammer with a sharpened edge as a saw, and being told it is an amazing tool for cutting down trees - told by all the other people around you that have never used a real saw.

[@hibcode]

So you are talking about an axe to cut down a tree?

[@JohnDoe-bu3qp]

I think Project Loom will kill most of the interest in reactive programming in Java because it will no longer be absolutely needed for max performance.

[@--Nath--]

Yeah, I have to wonder who would willingly go down that path if the jdk has magic built in.. Stack traces from hell, or just spin up a baby thread (virtual thread).

[@robchr]

As far as I know, Project Loom doesn't provide an observable stream of values like an Observable or Flow. I think there will still be a need for libraries like RxJava for this use case.

[@JohnDoe-bu3qp]

@@robchr That's fair, I was thinking more of reactive Rest API code.

[@Deahtstroke]

Update: Project Loom is great and all but the response times for Project Reactor are way better still because of its asynchronous nature.

[@JohnDoe-bu3qp]

@@Deahtstroke That's interesting, I wonder if that is something that will be improved over time...