Ged Haywood wrote:
Hi all,
On Thu, 31 Oct 2002, Iain 'Spoon' Truskett wrote:
experimenting with perforce [which, so far, appears nicer than CVS] )
Yikes! Josh, you got anything to say about that?
Well I have used perforce much more than CVS now, so that is where
I'm most comfortable.
My basic feeling is that perforce is harder to set up, but more
idiot proof while using it, especially for more advance operations
like branching & integration.
CVS however is a breeze to set up, but I feel like its branching
& tagging is more of a hack ( note I am just starting to use it
recently. ) I really like how I do not have to explicitly "cvs edit"
files like I do in perforce before I start working on them.
Oh, & CVS is free which is always a good thing. :)
As for scaling, perforce probably has a better chance to scale
with its dbm based storage & locking, however at this one company
that uses it they get db corruption when developers hammer
its with huge media checkins which I suspect CVS never would get.
Regards,
Josh
________________________________________________________________
Josh Chamas, Founder phone:925-552-0128
Chamas Enterprises Inc. http://www.chamas.com
NodeWorks Link Checking http://www.nodeworks.com
