<story><title>Anu: A sound, distributed version control systema</title><url>https://anu.dev/</url></story><parent_chain></parent_chain><comment><author>dan-robertson</author><text>It seems this was posted very shortly after the webpage became live and that the website is probably not in a fully fleshed out state. Therefore it’s missing some details. Probably the website is mostly targeted at people who already know what pijul is.&lt;p&gt;Here are some attempts at short descriptions of what I think this aims to achieve:&lt;p&gt;- pijul 1.0. A stable repo format with performance problems resolved and a good foundation for further work&lt;p&gt;- darcs except the algorithm is more convincingly correct and merges don’t take exponential time&lt;p&gt;- A version control system where certain things behave in reasonable ways avoiding potential strange behaviour, eg it doesn’t matter what order you merge things in, you always get the same result.&lt;p&gt;- A version control system that provides a good user interface to humans, a simple mental model, and asymptotically good performance.</text></comment>
<story><title>Anu: A sound, distributed version control systema</title><url>https://anu.dev/</url></story><parent_chain></parent_chain><comment><author>ChrisMarshallNY</author><text>Good luck. I mean that.&lt;p&gt;Git isn&amp;#x27;t perfect, but I&amp;#x27;ve been using version control since Apple Projector (in the late 1980s), and Git has done the best for me. I&amp;#x27;ve been using it for many years.&lt;p&gt;I don&amp;#x27;t miss Projector one tiny bit.&lt;p&gt;VSS (Visual SourceSafe) was a dog. It was direct file-based, and server connections would get &lt;i&gt;very&lt;/i&gt; busy. It was the old-fashioned kind, with the need to check out files.&lt;p&gt;But it had one very cool feature: You could create &amp;quot;aliases&amp;quot; of repo components; essentially creating a virtual repo that pointed into several other repos, taking just a couple of files from each.&lt;p&gt;I could see how that would be a technical nightmare to implement, but I like it a lot more than &amp;quot;the whole kit &amp;amp; kaboodle&amp;quot; approach that Git takes.&lt;p&gt;I also used Perforce for many years. It was a robust and dependable system, but had that need to check out files to work on them, and that drove me nuts.&lt;p&gt;I like Git, because it is &amp;quot;team-friendly,&amp;quot; and has a really light touch. It encourages many small checkins, which is how I think I should usually work.&lt;p&gt;I wish it handled big files better, but that&amp;#x27;s not really a big deal to me. I think this might be why Perforce is still preferred for game development (their asset libraries get &lt;i&gt;big&lt;/i&gt;).&lt;p&gt;Oh, also Submodules &lt;i&gt;suck&lt;/i&gt; like a supermassive, galaxy-core black hole.</text></comment>