When comparing CVS - Concurrent Versions System vs Perforce, the Slant community recommends Perforce for most people. In the question“What are the best version control systems?” Perforce is ranked 9th while CVS - Concurrent Versions System is ranked 16th.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Multi platform availability
Pro Central repository/server
There's a central repository and a clear path/protocol how to reach it.
Pro HelixCore
Helix Core for GIT large files is free for up to 5 users.
Pro Solid workflow for binary files
Perforce has shown itself as very capable when it comes to managing binary files. That's why it's still the go to version control system in game development.
Pro GUI and Visual Studio integration available
Cons
Con Ancient and outdated
CVS is an ancient version control system that was a very useful tool back in the days, but a lot of progress has been made since then. Recommending CVS today would be like recommending typewriters instead of computers for writing.
Con Closed Source
Con Does not work offline
You must be connected to the internet to do anything useful. Although, there is a Git <-> Perforce bridge that sorta solves the problem.
Con Centralized
Branching becomes a pain due to its non-distributed model.