[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Perforce versus Subversion

From: <Chris.Fouts_at_qimonda.com>
Date: 2006-08-22 15:25:35 CEST

Subversion is FREE, Perforce is NOT for "commercial"
use. End of evaluation IMHO, agin for commercial use.
I'm not saying that makes Subversion "better", but
it does the job adequately - except for cumbersome
branching/merging.

I've evaluated BOTH, and chose Subversion at work
ONLY for that reason. If only for personal use, I'd
probably use Perforce.

Perforce supports a "configuration spec" idea, similar
to Clearcase (but not quite) though, which neither CVS
nor Subversion sadly do NOT.

-chris

>-----Original Message-----
>From: Kenneth Porter [mailto:shiva@sewingwitch.com]
>Sent: Monday, August 21, 2006 6:27 PM
>To: users@subversion.tigris.org
>Subject: Perforce versus Subversion
>
>A coworker pointed out this document on the Perforce website:
>
><http://www.perforce.com/perforce/comparisons/perforce_subversion.pdf>
>
>Except for the benchmarks reported, Perforce just claims to do
>things differently (but worded in a way to make it sound like
>they're better, if you know nothing about Subversion or FOSS).
>
>Has anyone responded to this?
>
>My biggest concern with a commercial product is a proprietary
>closed data format. The Subversion dump format gives me a lot
>of peace of mind on this issue. I haven't seen any indication
>that Perforce offers something comparable.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 22 15:28:28 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.