Project Loom? Better Futures? What’s next for JVM concurrent programming
summary
Project Loom introduces virtual threads and continuations to make thread creation and blocking cheap, and it retrofits blocking APIs (InputStream, writers, sleep, semaphores) so blocking a virtual thread doesn’t block kernel threads. Examples compare blocking-style HTTP calls vs CompletableFuture-based async code and a cache-vs-database race with a 100ms delay; Loom restores useful stack traces but doesn’t remove the need for higher‑level declarative concurrency libraries like IO/ZIO or actor/stream toolkits.
AI-written summary · about
chapters (17)
- 0:00Start
- 1:36State the Problem
- 2:36Examples of Concurrency
- 5:06The Current Situation on the Jvm
- 14:42Compose Futures sequentially
- 16:04Blocking Operations
- 18:32Project Loom
- 18:55Virtual Threads
- 24:13When Is Loom Coming to Java
- 26:54The Problems with Threats
- 31:40Declarative Concurrency
- 41:55Ios Data Structures
- 42:48Cancellation
- 45:41Thread Interrupt
- 48:38Declarative Approach
- 52:20Kotlin
- 54:54Benchmarks
related talks
32mProject Loom? Better Futures? What’s next for JVM concurrent programming
50mProject Loom: Helping Write Concurrent Applications on the Java Platform
51mWhat's Looming in Java The Why and What of Project Loom
44mLoom: Revolution or Implementation Detail?
43mProject Loom: Fibers and Continuations for the Java Virtual Machine
47mConcurrent and Asynchronous Programming: Loom in Java 20 and 21
42mProject Loom Update
39mProject Loom: Modern Scalable Concurrency for the Java Platform