( Last Modified: 2008 November 03rd 11:58 AM )
Perforce is a Software Configuration Management System (SCM), made by this company: http://www.perforce.com/
Perforce does things a little differently than the majority of the SCMs out there. And there is no shortage of compaints with this system.
However I think what perforce is attempting is to be more than just a Software Configuration Management System, and also provide a Developer communication system. At any time developers can see who is editing a file, and display to others what files they are editing. This requires a changes in the SCM workflow that many including myself dislike and presents technical limitations to what Perforce can do.
I think the best thing that perfoce could do to improve its software is to make this "communication" system optional rather than mandatory. Such that it is not in the way 99% of the time, but when a developer want to display to others what file they are editing they have the tools available.
My own "Why Perforce Sucks" collection
Not Patch Friendly
http://www.diamand.org/perforce.html
Backing out Changes hard
http://www.redhillconsulting.com.au/blogs/simon/archives/000358.html
No LineEnd "None" option
http://smithii.com/perforce_bugs
Merging is painful
Revert files from a changlists without modifying the working copy of the files
p4 revert -k
http://www.perforce.com/perforce/doc.current/manuals/cmdref/revert.html
Add Reviews / Notifies in P4win
