Viewing profile — GermanJablo

Interesting. I'm the author of DocNode, a library that does exactly what you're describing; it might be useful. https://docukit.dev Cheers!

> A central server doesn't remove the need for this data though! Yes, it's possible. The problem is that we're using different definitions of what OT means. This conversation has c…

The root of our misunderstanding or debate is clear: although CRDT is fairly well defined, I don’t think the same is true for OT. What I have in mind is what I mentioned earlier: >…

> Citation needed It seems to me the burden of proof is on you. You were the one who claimed that “CRDTs perform better than OT-based systems.” I’m simply denying it. My reasoning …

Ok, replace "P2P restriction" with "idempotent, commutative restriction". > For example, OT has a tradeoff where you can discard old operations. The cost of doing so is that you ca…

Nowhere does it say it's multiple CRDTs. It says "isn't a single CRDT" and that "it's inspired by multiple separate CRDTs." A bit confusing, I agree. By the way, I work at Figma.

> But with some optimisation work, CRDTs perform better than OT based systems. I read your paper and I think this is a mistake. You assume that OT has quadratic complexity because …

The biggest evidence for collaborative editing is the immense popularity of Google Docs, Notion and Figma. Just because programming code isn't a good use case for automated conflic…

> (1) we found (contrary to popular belief) that OT actually does not require a centralized server In theory, yes, but in practice, any OT that operates without a central server (o…

> You don't think Figma is a serious application? I don't know where this popular belief came from. The Figma blog literally says "Figma isn't using true CRDTs"[1]. > The only real…

Thanks! I've recently made some improvements to the documentation. I agree the synchronization section could be improved more. I'll keep your feedback in mind. If you'd like to try…

Author of DocNode here. Yes, it’s still early days. But it’s a very robust library that I don’t expect will go through many breaking changes. It has been developed privately for ov…

Yes, the undo issue is a known bug in the website demo because it's messing with Lexical's undo functionality. It's not actually a DocNode bug. I'll fix it soon. The feedback about…

I remember reading Part 1 back in the day, and this is also an excellent article. I’ve spent 3+ years fighting the same problems while building DocNode and DocSync, two libraries t…

The tombstone problem is exactly why I built DocNode. You're right that you can't compact them without consensus, so DocNode just doesn't create them. It assumes a server decides t…

Interesting! I'm the author of https://docnode.dev and I see some similar concepts

Thank you so much for your help! I followed your advice: https://news.ycombinator.com/item?id=46211551

Hi everyone! After two years of development, I’m excited to announce DocNode: a type-safe, fast, ID-based Operational Transformation (OT) framework for conflict-free collaborative …

I think it's debatable what constitutes an "operation". In a CvRDT, a delta or diff can be considered an operation. In an ID-based OT, it can be considered that there is a transfor…

Thanks for the advice. I'll try it when the post is a week old. I hope it doesn't get rejected.

I think there's a misunderstanding here. People often associate CRDTs with IDs and tombstones, while associating OTs with positions. This is incorrect. What makes them different is…

That's an interesting idea. A "bring your own cloud" provider could be used for DocNode Sync. For example, Dropbox. Dropbox doesn't have the ability to resolve conflicts, but it ca…

Thanks! The answer depends on what you want: 1. Do you care about resolving concurrent conflicts? That is, if two users modify the same document simultaneously (or while one is off…

Hi everyone! After two years of development, I’m excited to announce DocNode: a type-safe, fast, ID-based Operational Transformation (OT) framework for conflict-free collaborative …