Unison, from a Scala perspective
summary
Unison replaces jar-based ABIs with content-addressed code where every term is identified by a hash and stored in a code database, eliminating many binary-compatibility failures. The workflow uses the UCM tool and Unison Share to install granular library terms, offering instant compilation, global hyperlinks, and deterministic disambiguation of names. Serialized functions expose dependencies so nodes request missing hashes and execute code remotely; the company cloud demo shows a 10-line deploy that builds and runs an HTTP service without Docker.
AI-written summary · about
chapters (9)
- 0:00Unison from Scala perspective
- 6:11Unison vs Scala uniqueness
- 9:22Live coding in Unison
- 14:03Code versioning in Unison
- 16:52Unison Share library management
- 20:46Unison for Scala developers
- 23:14Unison distributed computing
- 24:19Unison Cloud applications
- 27:28Conclusion on Unison
related talks
48mShoehorning dependency injection into a FP language - What does it take?
28mCode Merging Using Transformations and Member Identity
18mDoing More with Less: Orchestrating Serverless Applications without an Orchestrator
30mPoly Monorepos, the Best of the Two Worlds
45mFree Your Monads and the Rest Will Follow
49mJava's Hidden Gems: Tools and Libraries
42mIntegrating Developer Experiences
53mCompiling like a boss!