Ipecac for the Ouroboros
summary
Proposes a file-system layer of pervasive virtual, immutable, statically typed, lazy and reactive files whose metadata can drive names and structure, not the other way around. Shows concrete examples: exposing Picasa face data as directories of images, a DB-backed single-copy store that presents many paths, and a proposal to serialize and migrate running processes via the namespace. Argues the design yields cached, concurrency-safe updates and continuous consistency across views using virtual paths and demand-driven computation.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:28Compatibility
- 1:53Syrup of Ipecac
- 3:41Credibility Slide
- 4:29Enthusiasm Slide
- 5:50What is Scala
- 7:02Acknowledgement
- 7:41Definitions
- 10:02Communicating
- 13:50Reactive Files
- 15:04Continuous Consistency
- 16:58Immutable
- 17:30Unmake assumptions
- 17:58Sources of inspiration
- 18:47Houses for things
- 19:24Farfetch
- 19:47Houses
- 21:09Other books
- 21:40Container Transparency
related talks
47mThe Meaning of LIVE
01h 01mClean Architecture
30mDistributed system design
26mBeyond Dapps and Code?
22mToward a Live, Rich, Composable, and Collaborative Planetary Compute Engine
40mReduce System Complexity with Data-Oriented Programming
56mYour Object Model Sucks & an Introduction to Resource Oriented Computing
35mSystems @Scale Summer Q&A Week 3