3 ms·

Eh, Perforce is too pleasant if we are really embracing enterprise; makes it too easy to do sensible things like use a git client. No, it has got to be SVN for

by jlgreco 14y ago

Eh, Perforce is too pleasant if we are really embracing enterprise; makes it too easy to do sensible things like use a git client. No, it has got to be SVN for maximum pain.

steveklabnik 14y ago
If you think SVN is 'maximum pain' then you haven't tried out the full array of actually bad VCSes. SVN is fine, if a little outdated-feeling.
- kyllo 14y ago
  Three words: Microsoft Visual SourceSafe.
  - ttrreeww 14y ago
    Rational from IBM!
    - tacticus 14y ago
      I worked at uni that wanted to push this onto the CSIT students :| Such a horrible dept
- jlgreco 14y ago
  Besides the "modern" VCS's, I've used SVN, CVS, Perforce, and done both manual patch management and patch management with Quilt. I am sure there are some VCSes out there I would hate more than SVN if I used them, SourceSafe I'm sure, but I would honestly use any of those others I just listed before SVN again. Yes, I consider SVN to be a devolution of CVS.
skeletonjelly 14y ago
The merge tool (p4merge) is a dream, I shoehorn it into any VCS I use including TFS.
MBlume 14y ago
You can use a git client with SVN pretty easily. Git is a far better SVN client than SVN is.