Project Loom — Friend or Foe of Reactive?
summary
Project Loom introduces lightweight threads and structured parallelism for Java to enable efficient imperative-style asynchronous programming. The talk explains why Loom does not replace reactive (functional) approaches, and describes how Loom can complement and improve the reactive ecosystem by making reactive systems simpler, more reliable, and easier to use.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 7:18Imperative approach problems
- 15:20CompletableFuture limits
- 25:18Reactive with Project Reactor
- 36:06Virtual Threads in action
- 47:26Reactivity vs Loom
- 58:25Summary
related talks
35mProject Loom – the Killer of Reactive Programming
32mProject Loom? Better Futures? What’s next for JVM concurrent programming
01h 00mProject Loom? Better Futures? What’s next for JVM concurrent programming
43mProject Loom: Fibers and Continuations for the Java Virtual Machine
44mLoom: Revolution or Implementation Detail?
42mProject Loom Update
35mUntangled: Sneak peek at Project Loom
50mProject Loom: Helping Write Concurrent Applications on the Java Platform