From the PDF:
"Perforce is architected first and foremost for speed."
Were that anything more than just marketing droid speak, I would
chuck out Perforce on the basis of that sentence alone. I want my
version control system to be architected first and foremost for
keeping all of my code versions secure. Speed is a secondary
consideration.
On 21 Aug 2006, at 23:26, Kenneth Porter wrote:
> 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 11:55:41 2006