Fossil VS darcs

Feedback to author: The diagram and explanation took a beat longer than normal to scan, since this buries a bit that it's not about the beautiful source control system called fossil shipped as a composition of modules: https://fossil-scm.org/home/doc/trunk/www/index.wiki Great diagrams, so of course that's the first thing a reader will skim. People biuld things based on git all the time, the diagram looks like... - Source: Hacker News / 4 months ago

There are (all too rare) tools that back those objects with git as well. And there's always fossil ... https://fossil-scm.org/home/doc/trunk/www/index.wiki But it's not git. :-(. - Source: Hacker News / 6 months ago

I don't think git should be the infrastructure of collaboration. It's good for long-lived artifacts, but isn't good for discussion, for rights management, ... Fossil (https://fossil-scm.org/home/doc/trunk/www/index.wiki) is of course better, but if git must remain, I believe the base infrastructure should be the mailing list. Patches, branches and releases can live inside a mailing list, it is naturally built for... - Source: Hacker News / 8 months ago

Have you spent much time using Fossil? https://fossil-scm.org/home/doc/trunk/www/index.wiki. - Source: Hacker News / 9 months ago

> To make things more complicated, they also use their a relatively niche version management system instead of git. Which would complicate making contributions (if they accepted them). The Fossil VCS actually has a page explaining why it was created, instead of just using Git: https://sqlite.org/whynotgit.html Honestly, a lot of those points make sense, especially how Git is perhaps a little bit more complex and... - Source: Hacker News / 12 months ago

Darcs [0] patch theory was a predecessor to OTs/CRDTs (and a predecessor to git as well; in some ways it is the "smart" to which git was named "dumb"). When it works and performs well it is still sometimes version control magic. Pijul [1] is an interesting experiment to watch, trying to keep the patch theory flag flying and also trying to bring in updates from OTs and CRDTs as it can. [0] https://darcs.net [1]... - Source: Hacker News / 3 months ago

Perforce. As for DVCS, the best one I've used is Darcs: https://darcs.net/ There are some sticky wickets (specifically, exponential-time conflict resolution) that hindered its adoption. Thankfully, there's Pijul, which is like Darcs but a) solves that problem; and b) is written in Rust! The perfect DVCS, probably! https://pijul.org/. - Source: Hacker News / 5 months ago

Well technically one alternative I am going to bring up predates Git by several years, and that's DARCS. Fans of DARCS have written plenty of material on Git's perceived weaknesses. While DARCS' Haskell codebase apparently had some issues, its underlying "change" semantics have remained influential. For example, Pijul is a Rust-based contender currently in beta. It embraces a huge number of the paradigms,... - Source: dev.to / almost 2 years ago

We already have the "haskell of version control", darcs, i.e. Nobody uses it. Source: over 2 years ago