Residential Programming without Mutable State
summary
Claims a working Clojure prototype that stores top-level forms as immutable snippets (S‑expressions plus a dependency list) addressed by hash‑valued dependencies, so merges become an ever‑growing CRDT‑like set and functions keep the exact code they depended on when saved. Demo shows Alice and Bob changing foo/f concurrently yet foo/g still calls the old F, so run results stay stable. Pulls ideas from Unison, uses a REPL/editor demo, needs a build‑master role for canonical releases, and tooling and bootstrapping remain rough.
AI-written summary · about
chapters (7)
- 0:00Introduction to residential programming
- 3:25Programs as tangible information
- 10:06Shared mutable state problem
- 16:33Immutable code snippets proposal
- 26:05Dynamic dependency management
- 31:03Tooling and source control changes
- 36:00Q&A on trade-offs and workflow
