CRDTs merge concurrent edits. Why not concurrent creation?
loro.dev
loro.dev
E.g. let's say two people edit the body element depending on the content of the Edit the best solution¹ could be to take both contents (in which order?), to just take one, to take neither or to merge them semantically into a new third thing.
Meaning there are two obvious ways of going for a better merging solution:
1. Retain the ambiguity (if there is one) and present it to the users and let them decide
2. Use an LLM to guess the intent of both edits and task it to resolve the ambiguity if resolveable
¹: with best I mean the the solution real humans merging text from two pieces of paper would chose
The right UX for scenarios where accuracy is essential is to let users know when they are offline. The offline-enabled approach is not suitable for a lot of situations.
I think we've gone far enough down the road of "we can solve all CRDT merge conflicts through technical wizardry" that the next steps are "what is the right merge conflict UX when people should be communicating?" not just "what can we solve technically and never show the user?"