I've implemented operational transform based systems several times, and every time I check out CRDTs I end up staying with OT. I find the complexity arguments

I've implemented operational transform based systems several times, and every time I check out CRDTs I end up staying with OT. I find the complexity arguments against OTs to be far, far overblown and mostly academic, and that OT is, for me, much easier to understand. The two big critiques against OT are transform explosion: you could have N^2 transforms. Except that not every operation pair interacts. I usually see just a couple of categories of operations: text, key/value, tree, and list, and they all only need transforms within a category. The second critique is around sequencing in a distributed system, but I've also never seen a production system that doesn't have a central coordinating service. With a star topology OT sequencing because simple. You don't even need a lamport clock, you can get away with a simple counter. Buffering at the clients simplifies even more. There's a great series of posts on collaborative editing by Marijn Haverbeke, the author of CodeMirror and ProseMirror, that are designed with OT in mind: https://marijnhaverbeke.nl/blog/collaborative-editing-cm.html https://marijnhaverbeke.nl/blog/collaborative-editing-cm.htm...