Overall Satisfaction with Perforce
Perforce, for many years, was the primary version control tool in our organization. In the product department, we recently have switched to different software, but we still use Perforce for custom projects. Perforce is integrated within a .Net environment (ASP.Net and ASP MVC projects). Perforce is very scalable; it can be used from small projects to enterprise level projects. It has a learning curve, but after spending some time, it allows for fast and easy use.
- Perforce Visual tool (P4V) is very extensive and pretty well organized. Perforce has a built in history tool.
- Very good history view: you can see when your code was last changed, committed, and by whom.
- You can add a lot of columns and history view, and sort a file by any of the columns.
- I was having a hard time learning it. Even if you are an experienced developer, there is some learning curve.
- Can be slow when working with large data sets at once.
- When working on multiple workspaces on the same machine, Perforce can make it difficult not to mess up the code.
Today's web based software makes them easier to integrate into a development process. JIRA with integrated Bitbucket as the versioning tool, is ahead of the competition. However for large organizations, Perforce is still a very good choice. GitHub can be used as free tool, but only for public projects. Perforce is expensive, but much more powerful than GitHub.
The files view and history view are very clear. You can configure the information you want to see by adding new columns (from very large set of options). It makes work on versioning very pleasant. I use it to see my last changes, then compare with the current version, or I can see who has overwritten my version and ask that developer for details of his/her changes. This history view also gives an easy way to compare two chosen versions and revert to the version you need in just seconds.