|
|
Login/Become a Member! | 3 Comments
|
| | Comments are owned by the poster. We aren't responsible for their content. |
Re: Interview with David Roundy of Darcs on Source Control
(Score: 1, Informative)
by Anonymous on Nov 25, 2004 - 08:54 PM
|
You are missing the point completely. When people talk about "distributed development" in terms of revision control, they mean _desynchronized_ development. If you're using such a system, it shouldn't matter who you are, or who the project "head" is, or when or how you did your development - you will be able to resolve the differences between your code and others as you go along, and will have the least possible amount of work to do when it comes to resolving conflicts. You start working when you want to. You submit patches when you want to. They get integrated when someone with enough authority thinks they should be integrated.
Aegis, on the other hand, completely prohibits desynchronized development. For example, the default Aegis configuration requires that I get permission from a designated project manager _even before I can obtain a copy of the source code for myself, so I can start working._ In fact, I would go so far as to say that Aegis is not a revision control system, but a "source code protection system." (Use Aegis for a couple of months and you will see what I mean.)
I just came out of hospital a couple of hours ago, and am feeling a little weak! So let me end by saying this. At the previous company for which I worked, I used Aegis for about four years and I can say that it is the most unpleasant, most restrictive and most buggy of the source control systems I have used: CVS, Perforce and Aegis. CVS is friendly and simple. Perforce is friendly but powerful. Aegis is powerful but really, really nasty to live with.
I'm looking forward to playing around with darcs in the near future.
|
|
|