Pick a (Effect) Lane: A comparison of direct-style Scala vs effect systems
summary
Compares SoftwareMill Ox (direct-style on Project Loom virtual threads) with Cats-Effect IO by showing a 12-hour tonkatsu-broth and 3-hour chashu implementation, the exact error cases, monitors and recovery actions, and how concurrency is started and awaited. Ox uses virtual threads + supervise/fork and capability-scoped resource use but lacks mock time so tests can’t fast-forward; Cats-Effect uses lazy IO, start/join fibers, Resource for safe release, and working time-mocking for millisecond tests.
AI-written summary · about
chapters (5)
- 0:00Direct-style vs effect systems
- 2:09Direct-style vs monadic types
- 13:05Handling failures
- 19:28Concurrency with threads
- 29:07Resource testing differences
related talks
01h 00mScala. The War of Effects. ZIO vs Cats Effect
42mA Tour of Ox 1 0 - Direct Style Concurrency and Resiliency
23mEffects types in Scala - how to choose one
58mEffect-Oriented Programming
42mThe making of an IO
43mThe Design of the Scalaz 8 Effect System
30mTroll Driven Development: Implementing Functional Effects by Way of Self-Lobotomy
40mCats Effect 3