This is brilliant. One of the best things I've read in a while. I find it striking that the author's 7 rules (at about 3/4 of the scrollbar on desktop) read mu

This is brilliant. One of the best things I've read in a while. I find it striking that the author's 7 rules (at about 3/4 of the scrollbar on desktop) read much like a manifest on functional programming. In particular: > The operations are the data. That strikes me as a sword to the Gordian Knot of distributed state. Data isn't some mutable black box you poke mutations into and prod and read. Data is the set of operations used to construct it. This feels to me like the principle underlying FP in general, event sourcing, reactor pattern, and of course these RDTs. Of course, this implies a chunk of Data is the causal history of the data (which in the physical world is strictly true). C'est ne pas un byte[]. The fun part comes in all the different ways to optimize going from the territory (all the operations on a data blob) to the map (the "realized" data blob, or view into the system). This also has flavors of quantum mechanics to me. Causality is anything you can get away with mutating before a meaningful observation occurs.