Why should you wake up tomorrow and start to learn Scala?
summary
Argues that Scala lets teams model domains with algebraic data types and build compile‑time‑checked DSLs using operator and extension methods, and shows frameworks actually written in Scala — Apache Spark, Kafka, Akka — so native Scala code avoids Python/RPC overhead. Demonstrates ZIO “blueprints” as serializable program‑values that compose, run distributed, and let tests advance virtual time (tests run milliseconds instead of waiting 3s). Notes slow compilation and past binary clashes but says tooling and ecosystem fixes mitigate them.
AI-written summary · about
chapters (7)
- 0:00Learning Scala
- 4:44Scala beyond Java
- 12:39Efficient modeling in Scala
- 25:10Scala for frameworks
- 39:15DSLs and program-as-values
- 53:33Why learn Scala
- 54:19Q&A: compilation & compatibility
related talks
42mBuilding Bulletproof Concurrent Applications on the JVM
56mThe Magic of Spark: How High-Level Pipelines Become Distributed Hardcore
41mPreparing Apache Kafka for Scala 3
54mWhat Does the Future Spark Have in Store for Us?
49mA Practical Introduction to Akka Streams
59mLet's Get Lazy
53mRefactor your language knowledge portfolio - we are what we can code in
01h 07mMyths about Spark, or Can an Ordinary Java Developer Use Spark?