Unwrapping IO: is it a path that you want to follow?
summary
Compares ZIO vs a direct-style on JVM with Project Loom, claiming Loom lets virtual threads be cheap (example: 10 million virtual threads in ~2s) and restores useful stack traces and simple syntax. Measures and tradeoffs: ZIO gives typed error channels, safe resource management, interruption semantics and composable concurrency; direct-style + Ox (v0.0.6) offers lower syntax overhead, structured concurrency and simpler APIs but needs discipline for safe interruptions, resources and error tracking. Practical demos and concrete APIs are shown.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:04IO evolution in Scala and Loom
- 15:07Syntax overhead Z vs direct
- 20:08Error handling Z vs direct
- 27:35Stack traces informativeness
- 29:00Function coloring problem
- 31:27Refactoring in functional effects
- 35:24Resource management Z vs direct
- 39:41Concurrency and supervision Z and Ox
- 44:02Handling interruptions Z vs direct
- 46:49High-level concurrency in Z and Ox
- 48:56Z vs virtual threads comparison
- 50:59Speaker's company and projects
- 52:45Scala Times and events
- 54:12Q&A
related talks
45mZIO: Next-Generation Effects in Scala
01h 28mAsynchronous and Concurrent Programming in Scala Part 1
52mComparing Approaches to Structured Concurrency
01h 53mAsynchronous and Concurrent Programming in Scala Part 2
01h 12mAsynchronous and Concurrent Programming in Scala Part 3
56mThe Making of an IO
01h 10mDeclarative Concurrency With ZIO STM
29mEnhancing Spark's Power with ZIO