Unison: A Friendly Programming Language from the Future Part 2
summary
A functional language where every definition has a content-addressed hashes identity, so names point to immutable objects and the codebase is an append-only distributed store. Remote execution uses a Fork primitive that sends a hashed closure and dependencies to a node pool for just-in-time deployment (the Fork mechanism raises an external handler to pick a node). UCM provides watch expressions, a visual codebase browser, algebraic abilities effects, patch-based edits, and documentation as code with evaluable, linkable docs; M2 adds a smaller/faster relational code format and faster runtime.
AI-written summary · about
chapters (16)
- 0:00Distributed systems struggles
- 1:08Unison’s distributed approach
- 2:11Shared protocols vs hash-based comms
- 3:38MapReduce on tree structure
- 4:40Why frameworks are complex
- 5:23Forking to remote nodes
- 7:29Documentation written in the programming language
- 9:35Rich docs and hyperlinks
- 11:22Computable docs format
- 12:29Live demo workflow
- 16:03Codebase Manager basics
- 17:52Defining functions without imports
- 21:20Name resolution and type inference
- 22:45Append-only patching
- 24:10Finding types and definitions
- 25:15M2 features
related talks
41mIntroduction to the Unison programming language
32mUnison, and why the codebase of the future is a purely functional...
36mConcrete Functional Programming
43mAn Imperishable Wonderland of Infinite Fun
56mFunctional Programming on .NET - The Best of Both Worlds
42mFunctional Programming in 40 Minutes
01h 32mDistributed functional programming
01h 44mFunctional Programming: Technical Reasons to Adapt