Blog Buzz
As people discover and use darcs, a number are expressing their excitement in their blogs. Here's a sampling:
allocPSA Source Code Workflow with Darcs (August 2008)
"We use darcs for source code version control because it provides spontaneous branching and cherry-picking. 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 (August 2008)
"Darcs 2 has some major new features and more importantly some great new ways to get more performance out of darcs. However, to truly make use of these improvements there are a few changes from a darcs 1 setup that are quick to make and well worth the effort."
Using darcs with FTP and without SSH (May 2007)
"Showing how to use darcs to keep a remote repository in sync with a local one with ftp and sitecopy"
Managing a Django project using darcs (March, 2007)
"The DVCS I've been most taken with is darcs. It's simple to get started with, and uses a unique patch-oriented approach which I find very natural... Most of what I say below applies to any version control system -- it's just simpler (in my opinion) with darcs."
Simple Darcs Tutorial (August, 2006)
"Taking version control to the next level."
First Steps in the Darc (March 21, 2006)
"I immediately saw the potential of this system."
Top Five(5) Reasons darcs Kicks Source Code Control .... (September 23, 2005)
"Reason #2 : Built in software delivery mechanism and email updates"
Why I like Darcs (September 14, 2005)
What Is Source Control and what is DARCS? (August 14, 2005)
"In our mind, after concurrent versioning, the next big thing in source control is distribution. This is the ability for team-mates to work on a "mini" source control database of their own..."
All the cool kids are using darcs (July 10, 2005)
"It looks like a lot of Lisp developers are moving their projects over to darcs now..."
svn is nice, darcs is better (May 4, 2005) Thomas Zander blogged about KDE switching to Subversion, but darcs would have been so much nicer.
"Its disconnected nature is my number one feature."
installed it, using it and loving it
"Installation on my Mac was straightforward."
Darcs and Arch revisited (March 02, 2005)
"Overall, I like darcs a lot. It's a simple system that seems to work well. When I say that darcs is simple, I really mean it."
Ruby Buzz: Looking at Darcs (Jan 24, 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 (Jan 20, 2005)
"You may want to use it even though you already have another system."
Delving into darcs (Nov 28, 2004)
"the ease of moving patches between branches is very compelling"
Integrals and Derivates: A discussion of Subversion, Arch and Darcs
"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
"darcs gets a reasonably good balance between allowing people to undo mistakes, and protecting them from accidentally losing work."
"darcs wipes the floor with CVS"
"I got enchanted by its charming simplicity."
Using darcs for the first time
"Darcs allows easy sharing of changes between working directories with no central server or repository, and with hardly any setup or administration."
It's mostly about Haskell, but states "darcs is a very nice distributed version control system that is easy to use (for CVS users) and has some nice features."
Darcs, a New Way of Source Management
"Darcs is a decentralized source control manager (SCM) that is similar to GNU Arch, but without the complex command line syntax."
"Arch is way more complicated than it needs to be" ... "Darcs doesn't have too much support for signing of patches."
"One nice thing about darcs is that branches are trivial to create."
"Enter darcs. I've been keeping an eye on it for awhile, and it looks like it's become quite stable, useful, and fast recently."
"I've converted 24 public projects from Subversion or Arch to Darcs, preserving full history. . . It all went very smoothly."
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."
http://www.oreillynet.com/cs/user/view/cs_msg/71647
- Keeping your life in darcs, pros and cons
Darcs troubles
darcs: a study in communication failure (August 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 (March 6, 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.