Essays
🔰If CRDTs (Conflict-free Replicated Data Types) are new to you, check out this previous post. There's a simple way to understand CRDTs: It leverages algebra to unmix the inevitable mixing of data when syncing over an unreliable network. Why are networks unreliable? For one, it'd be
crdt
🔰If CRDTs are new to you, here are some introductory links. - An interactive intro to CRDTs [https://jakelazaroff.com/words/an-interactive-intro-to-crdts/] - An introduction to state-based CRDTs [https://www.bartoszsypytkowski.com/the-state-of-a-state-based-crdts/] - CRDTs for non-academics [https://www.youtube.com/watch?v=vBU70EjwGfw] - CRDT: The Hard Parts [https:
crdt
🔰If CRDTs are new to you, here are some introductory links.  - An interactive intro to CRDTs  - An introduction to state-based CRDTs  - CRDTs for non-academics  - CRDT: The Hard Parts  - Readings in CRDTs  - crdt.tech What are the trade-offs between different kinds of CRDTs (Conflict-free Replicated
lab notes
I been reading various papers on CRDTs to deepen my understanding of them. That's when I happened upon a paper that constructed Merkle-CRDTs from Merkle-DAGs [https://arxiv.org/pdf/2004.00107.pdf]. > Surprisingly, the internal merkle data structure of Git is like a vector clock. It establishes
lab notes
In the course of building the demo todo list local-first app, I've found that different CRDT libraries have different assumptions about the data access pattern you're using. Automerge [https://github.com/automerge/automerge] and Yjs [https://github.com/yjs/yjs] prioritize text editing, but Automerge assumes