2 ms·
I asked about this in another thread. It seems like all the blockchain does in this scenario is allow colliding edits to be detected for a fast retry. In an env
by KirinDave 10y ago
I asked about this in another thread. It seems like all the blockchain does in this scenario is allow colliding edits to be detected for a fast retry. In an environment with slow network I don't see how this would work well.
If that's the case, something like treedoc[1] is prescribed and it renders the blockchain part of this irrelevant unless we're concerned about sourcing edits (which treedoc or a similar CRDT would be entirely amenable to and even appreciate).
I was sort of hoping that there was something I didn't understand about the algorithm that helped here.
Also, what is "OT stuff"?
- davidbanham 10y agoOperational Transform stuff. It's what makes Google Wave chooch and is also the heart of sharejs.
- KirinDave 10y agoThanks. Yeah I finally realized that's what people were talking about. I don't entirely understand the appeal in 2017, it seems like it gives worse performance, worse guarantees, and is more complex than the equivalent CRDT.