CRDTs: The Hard Parts [video]
Does anyone take issue with the fact that CRDTs seem to require keeping a history of every change ever made to the document?<p>Seems like it could get unwieldy very fast. Especially, in the face of a bad actor spamming a document with updates.<p>I've considered using CRDTs in a few projects now, but the requirement to keep a running log of updates forever has ruled them out.  I've ended up using other less sound (more prone to failure), but more practical methods of doing sync.<p>Perhaps, I'm missing something.  Wouldn't be the first time.<p>Are there alternatives without this requirement, or that would at least allow a cap on the update log?