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.
-
-
-
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 more reply
New conversation -
-
-
In which editor did you write it? :)
-
I just banged this out in the web interface, heh.
End of conversation
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.