Pijul: A intuitive VCS unlike Git that's based on sound theory of patches

Re:Pijul: A intuitive VCS unlike Git that's based on sound t... by Zanfa on Saturday September 26, 2020 @04:37PM (#24601904)

All CRDTs are fundamentally asychronous, theres no requirement for them to be used in a Google Docs live editing type of setup, so as far as conflict resolution goes I still don’t see any major difference between this conflict resolution strategy and WOOT (aside from character vs line-level units).

It also suffers from the same problem as WOOT that while it’s mathematically (merge) conflict free, you still need to resolve semantic (merge) conflicts before the result is sensible, like in the final example.

[ Parent | on HN ]

Re:Pijul: A intuitive VCS unlike Git that's based on sound t... by pmeunier on Sunday September 27, 2020 @06:48AM (#24605703)

> All CRDTs are fundamentally asychronous

I didn't say otherwise. However, Google Docs and WOOT are meant to be used "almost synchronously" (which is why I wrote "almost synchronous" in my answer), in the sense that conflicts are presented to the user almost instantly.

By the way, in the paper you mentioned, the words "synchronous" and "real-time" are used to describe WOOT.

[ Parent | on HN ]