Perforce Sucks

Seriously. What's the deal with Perforce? I have a local "workspace" which is all of the source code files, but the Perforce client sets them all to read-only. If I want to edit one of these files I have to manually check it out with the Perforce client, which then sets the file permissions to read-write. And when I'm done I commit the changes which sets the file back to read-only.

So, what does the read-only / read-write crap buy you? Nothing. In the end, if someone else has checked out the file while you were editing it (which can occur), you have to merge your changes. You have to do that in any revisioning system. So why go through the idiotic manual step of check-in / check-out?

And I'm going to have to do this process hundreds of times a day. Every day.

Subversion. Git. I'd even take CVS over this garbage.

I'm going to get a new job when this contract is up.

I'm also going to put on my resume, "not interested in jobs which require Perforce".

Subscribe to A garage sale for your mind

Don’t miss out on the latest posts. Sign up now to get access to the library of members-only posts.
[email protected]
Subscribe