4 ms·
> Drawpile solves the second problem in the most simple way possible: all edits go through a central server, which distributes them to all connected clients (in
by zffr 5y ago
> Drawpile solves the second problem in the most simple way possible: all edits go through a central server, which distributes them to all connected clients (including the originator) in the same order. So, when a client receives commands from the server, it knows all the other clients also received, or will receive, them in the same order.
You don't need CRDTs if you have a centralized server and require clients to be connected to make edits. CRDTs are useful when you want to enable collaboration in a decentralized way.
- colesantiago 5y agoSo does this mean Figma is decentralized since they are also using CRDTs?
- nh2 5y ago"You don't need X for centralised" does not imply "if you have X then you're decentralised". Beyond that simple logic: https://www.figma.com/blog/how-figmas-multiplayer-technology-works/ https://www.figma.com/blog/how-figmas-multiplayer-technology... > Figma isn't using true CRDTs though. CRDTs are designed for decentralized systems where there is no single central authority to decide what the final state should be. There is some unavoidable performance and memory overhead with doing this. Since Figma is centralized (our server is the central authority), we can simplify our system
- colesantiago 5y agoInteresting, so this must mean that Figma must be using CRDTs wrong then, but it works for them anyway since they aren't using "true CRDTs".
- pc86 5y agoMaybe CRDTs (or more precisely, their implementation of them) give them some other benefit beyond the disregarded ability to be decentralized. It doesn't necessarily mean they're using them incorrectly.