Project Loom - A Friend or Foe of Reactive? - Oleh Dokuka, VMware & Andrii Rodionov

Project Loom - A Friend or Foe of Reactive? - Oleh Dokuka, VMware & Andrii Rodionov, National Technical University
We heard about Project Loom - the new programming models on the Java platform for high-throughput lightweight concurrency and threading. Project Loom will give a structured concurrency in Java which enables writing efficient async apps using imperative paradigm. With that, many started questioning whether the Functional and Reactive approach remains with that in the Java ecosystem. In that talk, we going to busters the myth of Loom killing Reactive and instead discuss how Loom will improve the Reactive ecosystem and make it more robust and simpler to use.

[@TomaszNurkiewicz]

0:00 Introduction
2:59 Sample use case
11:19 CompletableFuture
13:42 Project Reactor
19:05 Project Loom
30:10 Loom + Reactive approach
34:01 Questions

[@hneres]

Great video. Realy seems that the combination between Loom + Reactive Frameworks will be very good.

[@michaeleaster1815]

This is a creative, entertaining talk: thank you. I enjoyed it very much.

[@alexandersmirnov4274]

Guys that was a great talk!!!
I hope we will see you again together on this topic.

[@rahuldeepattri9244]

This really helps in understanding reactive programming better!

[@alex.shmalex]

This talk didn't age well after structured concurrency. Loom is going to kill reactive programming. Amen.

[@spheenik]

"After" structured concurrency? It's only in Incubator at the moment. And while you can certainly reimplement something like Reactor on StructuredTaskScope, the multitude of operators you have already production ready in Reactor that allow you to define your pipeline will look very ugly if you just build it up "in place" with StructuredTaskScope. So, I beg to differ, Loom is not going to kill it (first time I ever disagree with Brian Goetz, ever!)