Automerge: a new foundation for collaboration software [video]

Post by aogaili » Sat, Dec 11, 2021, 3:22 PM UTC

jpgvm wrote: post #19

aogaili wrote: post #12

MeteorJS solved this 12 years ago...but good to see more thoughts being put into this.

It did not at all. It solved the problem of how to reflect a source of truth (the server) in somewhat real-time on the client through subscriptions. Also made some attempt to have edits that were persisted to client-side mini-mongo pushed to the server but this was best effort at most. CRDTs are on a completely different level. They provide deterministic conflict resolution strategies through either/or causal and phy…

Post by aogaili » Sun, Dec 12, 2021, 2:23 AM UTC

jpgvm wrote: post #32

aogaili wrote: post #31

Earlier quoted context omitted.

I understand the difference. However, the local mini-mongo is acting a local-state and the JSON/JS all the way is solving the marshalling/ORM issue. I understand it is a centralized way of dealing with this, however, it was operating on the same problem space. Furthermore, automerge can be used as the server, which bring it closer to what Meteor did. I was hinting at the overlap in the problem space, but I should hav…

You can't just use automerge on the server, it must be used on the client and additionally on the server (or a more cut down version that just replicates deltas between peers). If you are going to try out automerge you should also take a look at y.js and diamond-types.