Not quite a blog post, but my thoughts on why CRDT didn't work out as well for xi-editor as I had hoped:https://github.com/xi-editor/xi-editor/issues/1187#issuecomment-491473599 …
-
-
Replying to @raphlinus
My takeaway 1. Don't experiment on too many things at once 2. Asynchronise the heavylifting: LSP, builds, tests, CI. Also, things that depend on human input, like code reviews. 3. Should not overuse CRDT for mundane local interactions. 4. CRDT is not a silver bullet.
1 reply 1 retweet 16 likes -
Replying to @gritzko @raphlinus
I spent 10 years in the CRDT land. I started before the term was introduced for that family of data structures. I may testify it is harder than it seems initially. Especially, in the absence of prior art.
1 reply 0 retweets 7 likes
Your takeaways here sound about right. I think there is a need for clear exposition on the tradeoffs; I haven't found the academic literature particularly useful. But this is not my hill.
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.