16 messages in com.perforce.perforce-user[p4] Is Perforce better than VSS?| From | Sent On | Attachments |
|---|---|---|
| Sven Olson | 14 Oct 1999 14:15 | |
| Mike Meyer | 14 Oct 1999 14:59 | |
| Todd LaWall | 14 Oct 1999 15:11 | |
| Jonathan Arnold | 15 Oct 1999 06:24 | |
| Nick Pisarro | 15 Oct 1999 06:56 | |
| Eric Scouten | 15 Oct 1999 07:06 | |
| Scott Blachowicz | 15 Oct 1999 08:28 | |
| Sven Olson | 15 Oct 1999 09:13 | |
| Scott Blachowicz | 15 Oct 1999 09:51 | |
| Sam Falkner | 15 Oct 1999 09:51 | |
| Robert Cowham | 15 Oct 1999 10:16 | |
| Raymond Wiker | 18 Oct 1999 02:47 | |
| Richard Brooksby | 19 Oct 1999 11:37 | |
| Nick Barnes | 20 Oct 1999 03:56 | |
| Frank Merrow | 20 Oct 1999 08:21 | |
| Nick Barnes | 20 Oct 1999 09:02 |
| Subject: | [p4] Is Perforce better than VSS? |
|---|---|
| From: | Eric Scouten (scou...@Adobe.COM) |
| Date: | 10/15/1999 07:06:36 AM |
| List: | com.perforce.perforce-user |
Speaking from direct experience I can confirm what Nick has said. I joined a 15-engineer team at Adobe about two years ago that was using VSS. After a year's work on a project, database corruption was a weekly occurrence. It brought our team to a screeching halt for an hour or more as we tracked down each client, logged them off, sent everyone off to go have lunch, ran the database repair program, and then (hopefully) brought it back up successfully.
In contrast, the same team has encountered only one significant failure of the Perforce database in the year and a half since they switched. That was due to a bug in the 'p4 obliterate' command which was fixed shortly after I reported it. (And... Perforce's customer support people helped me repair the database damage that was caused by the bug. Can you imagine MS doing that?)
In the last year or so, almost all of Adobe's application development teams have switched from VSS to Perforce. Given the distributed nature of our company (development teams in Seattle, Minneapolis, Boston, India, several locations in California, and individual contributors scattered across the country), it has suited us well.
At 10/15/1999 08:57, Nick Pisarro wrote:
sventolson at yahoo.com writes:
I'm looking to the Perforce user community to learn about the differences in the products and the pros and cons of switching to Perforce.
I believe previous discussions in this conference have indicated that VSS is a lot less robust that Perforce. It is a lot easier for your source repository to become corrupt with VSS.
I also understand Perforce handles branching and merging much better than VSS.
I have no direct experience with this--only with what I have read here, however. Perhaps others can give you more authoritative information.
Nick Pisarro, Jr. Aperture Technologies, Inc.
_______________________________________________ perforce-user mailing list - perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user
__________________________________________________________________________ Eric Scouten <eric at scouten.com> Software engineer @ Adobe Systems THIS MONTH on www.scouten.com (Aug '99): Landscape & nature photography
* Lightning! (2 slides) * Garden tour (29 slides) * Four desktop images
__________________________________________________________________________
I find myself up my stream of consciousness without a paddle. -Kevin Kling