From: Bob Hutchison Date: 2006-01-04T01:28:44+09:00 Subject: Re: Ruby projects and interfaces to revision control systems (Darcs vs. Cogito) On Jan 3, 2006, at 9:26 AM, Alan Garrison wrote: > Our company, which is beginning to use Ruby in production systems, > has been using Darcs[1] for a little while with general success. > My co-worker has even released a preliminary ruby-darcs interface > on RubyForge. However, a few of Darcs bottlenecks have come up and > we've also run across the Cogito[2] project. I've seen that Darcs > has gotten a fair amount of attention in the overall Rubysphere, > but I don't recall reading anything about Cogito. From either an > ordinary SCM standpoint for maintaining Ruby projects or using Ruby > to interact with the SCM, has anyone chosen Cogito over Darcs? This is tough (I'm going through this process myself right now). Basically I think the non-commercial contenders are CVS, SVN and darcs. I can't see how someone would go with CVS given SVN (we use CVS for historical reasons only and want to move to something better). SVN is a modern CVS and I don't mean that as a slight. Darcs is different. It is based on a very nice theory of change sets. It is really easy to use and trouble shoot. Written in haskell -- this is no negative from my point of view, and really, who mucks about with their source control system so who cares what it is written in? Cognito... git... why? I can't think of a single reason (unless you are working on the linux kernel). SVN is probably the conservative choice. Darcs might well be the right choice. Cheers, Bob > > > [1] http://www.darcs.net/ > [2] http://www.kernel.org/pub/software/scm/cogito/README > > > -- > Alan Garrison > Cronosys, LLC > Phone: 216-221-4600 ext 308 > > ---- Bob Hutchison -- blogs at Recursive Design Inc. -- Raconteur -- xampl for Ruby --