Pijul: Version-Control Post-Git [video]
I really like the idea of a version control system based on commutative patches but I&#x27;m just not seeing how it&#x27;s going to translate to a system that&#x27;s intuitive and easy to use not just for programmers, but also for lawyers and artists.<p>Consider a patch like this one, titled &quot;Solving conflicts&quot;:<p><a href="https:&#x2F;&#x2F;nest.pijul.com&#x2F;pijul&#x2F;pijul&#x2F;changes&#x2F;2MLOE3FPVT4ZXC4L74VC7GV2IXATZQNFLJECDPZZ7MTSW4A6XT5QC" rel="nofollow noreferrer">https:&#x2F;&#x2F;nest.pijul.com&#x2F;pijul&#x2F;pijul&#x2F;changes&#x2F;2MLOE3FPVT4ZXC4L7...</a><p>&quot;Solving an order conflict&quot; and &quot;Resurrecting zombie bytes&quot; sound like the tricky parts of the patch-based workflow. I would very much like to understand how to work with these parts of Pijul. How are these actions performed? How does the user interact with the graph to perform these actions? Is the conflict state rendered into the file? It&#x27;s not mentioned in the video, and I cannot find it in the documentation or in blog posts.<p>I cannot be the only one that&#x27;s interested in learning about those things, and I think it would be more effective than anything else in raising interest for Pijul.<p>My best guess is that the workflow is still rough around the edges and requires the user to have a good understanding of the underlying graph, and therefore it&#x27;s not ready to be presented yet. And my hot take is that it&#x27;s still rough around the edges because there is no easy way, and maybe no way at all, to make it polished and intuitive for a new user. But I want to be proven wrong.