Complex Problems, Simple (build)tool
summary
Scala CLI demonstrates a deliberate tradeoff: it delivers fast, click-to-run compilation, tests, packaging and native-image builds with using directives embedded per file and a command-line-first configuration model, but it is single-module only and exposes no internal plugin API. Demoed workflows include JVM run, native image and test runs; an ad-hoc multi-module pipeline shows ~1s Scala CLI steps versus ~2s with SBT. An experimental orchestrator (blip) aims to add workspace composition without reintroducing plugin complexity.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:51SBT
- 4:40Scala CLI
- 7:52Scala CLI Limitations
- 11:01Scala Multimodule Support
- 11:26Scala SBT
- 14:53Scala Mill
- 16:18Gradle
- 16:28Gradle Enterprise
- 18:08Expectations for the future
- 20:50Unicorn and Rainbow
- 21:30Rust and Go
- 23:56Scholar CLI
- 25:23Extensibility
- 28:18Scala CLI extension
- 31:00Blip
- 31:47Why
related talks
47mManaging micro libraries with Scala CLI
58mNext generation Scala builds with CBT
32mBetter Scala builds with the Mill build tool
41mCBT A New, Intuitive Build Tool for Scala
29mExploring Scala Tooling ecosystem
38mFork It Harder Make It Better
19mExploring Scala Tooling ecosystem
39mMeet Bloop and Get More Productive with Scala