Within the contents of the paper, it talks about CRDTs to technically implement it.
I'm not familiar with the technical tradeoffs but I bookmarked some past HN threads mentioning CRDT did not fare as well as OT (Operational Transform):
Within the contents of the paper, it talks about CRDTs to technically implement it.
I'm not familiar with the technical tradeoffs but I bookmarked some past HN threads mentioning CRDT did not fare as well as OT (Operational Transform):
This has only really started being true in the last year or so.
https://github.com/automerge/automerge-rs
I'm hoping this matures a bit more in the next months, seems really promising.
To be clear, I think this is exciting stuff and your article is great. I'm just curious if there are any open research problems in this area that would make them more appealing in production.
So on the server I'd rather have a native implementation - which would also remove the need to bundle a JS VM in databases. And if we have that, it should be pretty easy to pack the same code into wasm for the browser.
And this is all assuming a JS-native web world. I also want CRDTs for native apps like Bear. And it'd be much easier to use a rust library than link to v8.
The following article shows that: