Existing users, 
 Perforce - 2009.1Version control system uses SCM protocol. |
|
||||||||||||||
|
|||||||||||||||
Feedback Summary:
| This Version: | |||||
| Overall Rating: | Not rated (0.0) | Features: | Not rated (0.0) | Support: | Not rated (0.0) |
| Ease of Use: | Not rated (0.0) | Quality / Stability: | Not rated (0.0) | Price: | Not rated (0.0) |
Key to Types of Feedback:
Reviews 
Troubleshooting 
Usage Tips 
Developer Notes 
Commentary 
Featured Reviews
All Feedback: 1 - 6 of 6
It's a pretty decent package 
- Version: 2004.2, 9/9/2004 01:15PM PST
mnb
I've been using Perforce on 3 different platforms for 5 months now. The concept of clients is a bit wierd compared to cvs and just checking out and editing a file can be a pain compared to cvs, but Perforce is more advanced than cvs.
If your buildmeister knows it or learns it, it's worth using. I don't know how much it costs, but it's definitely more powerful than cvs. And SourceSafe plain sucks. I haven't looked at Subversion and doubt I will since I don't implement version control, I just use whatever we have where I work.
If your buildmeister knows it or learns it, it's worth using. I don't know how much it costs, but it's definitely more powerful than cvs. And SourceSafe plain sucks. I haven't looked at Subversion and doubt I will since I don't implement version control, I just use whatever we have where I work.
Hard to use, very expensive, and very "closed" - Version: 2004.2, 9/9/2004 12:28PM PST
dylan3--2008
A few months ago, I was looking for something better than CVS. I heard good things about it, so I tried Perforce. I'm an experienced Unix guy, but I had a hard time installing it. After installing it, I had a hard time using it. (I'm used to CVS, so I thought I was used to hard-to-use version control systems). Finally, after giving up, I found it hard to extract my life out of Perforce.
Then I heard about Subversion. In contrast to Perforce, Subversion was easier to install (though not easy yet), and MUCH easier to use. Plus, it's free! http://subversion.tigris.org/
Then I heard about Subversion. In contrast to Perforce, Subversion was easier to install (though not easy yet), and MUCH easier to use. Plus, it's free! http://subversion.tigris.org/
Most Recent Replies: View All 2 Replies
- Hard to use, very expensive, and very "closed"
So far so good - Version: 2003.2beta/50527, 1/13/2004 09:55AM PST
hiroshi1
We have been using the Windoze version here for a while and it is great way to track the changes and updates in the product development. I have been using the beta 2003.2 version under Panther for a few months and it is great. I just updated to 2003.2 and so far so good, no real problems I have found. We have about 100 users, using W2K, XP, OSX, and Linux, and they all work seamlessly together.
Adam - Fortunately… - Version: 2002.2, 3/5/2003 01:41AM PST
Chief Aesthetician
there already is a great cocoa port of the perforce GUI out there. You should be able to find it here on version tracker. It's appropriately titled P4Cocoa.
It's a real… - Version: 2001.1/24200, 6/1/2002 05:41PM PST
(0 of 1 users found this comment useful)
Adam Randall
shame that they only have a GUI to this in Windows. Having to use command line tools is okay, but the speed of managing files on Windows just makes look that much more archaic. Oh well, time to learn Cocoa and make my own =)
I would not consider it freeware, as if you choose to use it 'for free', you are limited to 2 users, and 2 client views, so unless you are by yourself or on a very small team, you need to pay a fair amount per user (and yearly fee's to upgrade the server to the latest version).
This is just a clarification, because the 2009.1 update page in versiontracker listed it as freeware, while the earlier 2004.x page has an actual price.
It's expensive compared to free (cvs, and now subversion, git, etc...), but cheaper than most of the competition. I've used it for 10 years, and the server has only crashed on me once (p4d), and I haven't lost even an update or got a corrupt file from the crash or multiple forced restarts of the machine hosting it. It's also got clients for a crazy number of platforms, including both a GUI client and a cli tool for Mac OS X, and it's supported within XCode. The initial learning curve for setting up and using the client is pretty high, and it may take a couple of projects for you to figure out the best way to organize the source in Perforce for your specific needs.
As a guidepost, I would rather kill myself than use CVS, I'm not a fan of distributed scm's like git or mercurial, I wouldn't touch Seapine's scm with a ten foot pole after having used TestTrack for years and having it crash with even light (as in 2 users) usage and corrupt it's databases multiple times, and haven't looked at systems that don't have a native Mac client. I may switch to Subversion now that they have improved handling of branches and there is more mature client software available, but there doesn't seem to be anything really compelling with it over Perforce other than it's free (server and basic clients).