Blog Buzz

As people discover and use darcs, a number are expressing their excitement in their blogs. Here’s a sampling:

• Darcs “I like darcs because it’s very easy to use, and more importantly, because I am well familiar with it.”
• Message-Passing Concurrency for Haskell using the CHP library (2010) “All my Haskell code lives in darcs repositories, and this post is intended to detail a little of how I use it.”
• Darcs Distributed Version Control (2009) “Darcs is the simplest tool to get your feet wet in the world of distributed version control.”
• Darcs 2: A major update
  2008. “The reality is that while some of the weaknesses of Darcs 1.0 were dealbreakers for some users, Darcs 2 is a solid, mature, usable release that deserves a second look.”
• allocPSA Source Code Workflow with Darcs
  2008. “Functionality that is usually considered to be an”add-on" for most DVCS’, we consider to be a necessary and fundamental part of running a distributed development project."
• A User’s Guide to Darcs 2
  2008. “Darcs 2 has some major new features and more importantly some great new ways to get more performance out of darcs.”
• Using darcs with FTP and without SSH (2007)
• Managing a Django project using darcs (2007) “Most of what I say below applies to any version control system – it’s just simpler (in my opinion) with darcs.”
• Simple Darcs Tutorial (2006)
• Top Five Reasons darcs Kicks Source Code Control ….
  2005. “Reason #2 : Built in software delivery mechanism and email updates”
• All the cool kids are using darcs (2005)
• Darcs and Arch revisited
  2005. “When I say that darcs is simple, I really mean it.”
• Ruby Buzz: Looking at Darcs
  2005. (or see original post, or the movie on the feedback wiki) “The number one feature I like is that it is damn easy to use without sacrificing power.”
• Darcs infected
  2005. “You may want to use it even though you already have another system.”
• Benefits from a real world switch from CVS to darcs (2005)
• http://gintasm.blogspot.com/2005/06/europython-2005-report.html “I use darcs for managing my code, and it has been great so far, much more pleasant to use that Arch and much more powerful than Subversion which I use at work.”
• Darcs, a New Way of Source Management
  2004. “Darcs is a decentralized source control manager (SCM) that is similar to GNU Arch, but without the complex command line syntax.”
• GNU Arch vs. darcs (2004) “I got enchanted by its charming simplicity.”
• Integrals and Derivates: A discussion of Subversion, Arch and Darcs
  2004. “Working in terms of changesets, or at least having the option to do so allows more powerful operation.”
• Forgiveness in Version Control, by Martin Pool
  2004. “darcs gets a reasonably good balance between allowing people to undo mistakes, and protecting them from accidentally losing work.”

Version Control Comparisons

Not necessary blogs:

• Comparison of revision control software, Wikipedia article
• DVCS Roundup: One System to Rule Them All (2009) part 2, part 3
• Better SCM Version Control Systems Comparison (2010)
• Whose Distributed VCS Is The Most Distributed?, by John Goerzen (2006)
• monde

Darcs troubles

• darcs: a study in communication failure (2008) ‘’The darcs revision control system has all but lost out to git within the past few months. A rather large part of the reason is a rushed and very poorly worded release announcement, following a rather long (I’m told 4 years; I haven’t been aware of it that long, which itself is perhaps ominous) post-1.0 silence from the darcs developers’’
• Reexamining Darcs & Mercurial
  2007. I continue to believe that it is the most distributed of the distributed VCSs, which is a Good Thing. However, I have lately started having trouble with Darcs hanging while working on my Debian packages.