Menu

Post image 1
Post image 2
1 / 2
0

Mergeable Containers: Fixing Concurrent Child Creation – Loro

Reading 0:00
15s threshold

2026-06-09 by Zixuan Chen Two users are offline. Both add content to the same empty note. They come back online, sync finishes, and one user’s edits seem to disappear. There is no error, and the data is not actually gone from history. But can only return one Text container. The other container was created concurrently and still exists in history, but it is no longer visible in the current document state. From the application’s point of view, this looks like data loss. This is a classic problem in JSON-like CRDTs. Users have run into versions of it in the Loro, Yjs, and Automerge communities. The Appendix has short scripts that reproduce it in all three. Loro now solves this with Mergeable Containers. They make a child container’s identity come from its logical position in the , not from the ID of the operation that happened to create it. Special thanks to Alexis Williams from Synapdeck for the substantial implementation work and design discussion behind this feature.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More