Document-oriented programming based on edit history
summary
Prototype document system stores program as an edit history and demonstrates three concrete behaviors: a local-first merge that reconciles concurrent edits (example: adding a speaker vs refactoring a list into a table), automatic edit-transformation of selectors so formulas update when structure changes, and evaluation-as-edits where evaluation appends generated edits which get invalidated and removed when later edits conflict. The demo is a working prototype with replay buttons, example tests that show pairwise merge equivalence for samples, but no formal proof yet.
AI-written summary · about
chapters (12)
- 0:00Document-oriented programming intro
- 1:05Accessible collaborative systems vision
- 2:33Everything as a document
- 4:01Programming as edit sequence
- 5:07Conference planning demo
- 7:55Merging conflicting edits
- 10:45Code and formulas in docs
- 13:12Step-by-step formula eval
- 16:46Store eval history in doc
- 18:34Invalidation on edits
- 20:24Future directions
- 22:54Q&A
related talks
11mDenicek: Computational Substrate for Document-Oriented End-User Programming
09mMicro-Versioning Tool to Support Experimentation in Exploratory Programming
45mResidential Programming without Mutable State
28mCode the Docs: Interactive Document Environments
04mLT Erich Studer
36mTo document, or not document that is the question
20mPlaying with Interactive Documentation
34mCode the Docs: Interactive Document Environments