I agree that full stack support is the missing pice that's need to make use explode. But I do think the current implementations will get there. CRDTs are fairl

I agree that full stack support is the missing pice that's need to make use explode. But I do think the current implementations will get there. CRDTs are fairly unique in that you need them to be exposed very close to the front of your stack in order to capture user intent, but you also need support further back in your stack for merging, replication, and querying. We have good front end support and there are multiple exciting projects building collaboration servers (PartyKit in particular looks awesome) for them. What I think is missing is support in database, that's what I've been experimenting with (below). If you are building an offline enabled app, having the ability to generate diffs and merge in database enables easy multi document sync. Also most general purpose CRDTs are a combination of JSON and XML like data structures, it's useful to be able to query the structures in your database. For example if you build a notes app that supports inline tags, it's useful to be able to query and index those from within the XML like structure without having to dump the whole thing out at another layer of your stack. Essentially, you need to capture user intent in the CRDT on the front end, but then have support through your whole backend. Yjs Postgres: https://github.com/samwillis/yjs-pg-test https://github.com/samwillis/yjs-pg-test Yjs SQLite: https://github.com/samwillis/yjs-sqlite-test https://github.com/samwillis/yjs-sqlite-test (These are just early experiments, I'm working on a cleaner shared implementation with support for various SQLite bindings, and better querying)