New paper, which @pvh and I wrote together: “PushPin: Towards Production-Quality Peer-to-Peer Collaboration”.
It's about our hard-won experience trying to build peer-to-peer local-first software using CRDTs. Very practical, lots of insights. Take a look! https://martin.kleppmann.com/papers/pushpin-papoc20.pdf …
One of my big questions in this space is how well the research generalizes beyond the collaborative text editing use case. Sure the sites converge, but is convergence enough? How well do application programmers need to understand the behavior of their particular CRDTs?
-
-
On that note, some of Ink & Switch's writing seems to conflate CRDTs generally and one or another of the large number of CRDTs that have been developed. "CRDTs accumulate a large change history, which creates performance problems" is not generally true.
-
I have heard rumors of usable state-based CRDTs but I have not found any implementations I could use. Would love to take one for a spin if you can correct my ignorance.
End of conversation
New conversation -
-
-
Not sure how to hammer those particular questions into paper-form, but roughly, we’ve built a trello clone, pixel art, chats, TODO lists, code components, and several cards-on-a-board, and I guess I’d say briefly the answer is “it seems surprisingly fine.”
-
I haven't checked in on Lasp recently, but it looked like a lot great work was going on in that project toward making a general purpose language based on CRDTs.
- 4 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.