Ah, Blessed Days of Subversion
… are over, because we moved our source code to Team Foundation.
Yea, verily I say unto thee, that is a modal dialog box.
So my Visual Studio is locked up — completely — until somebody gives the server the kick it deserves.
I did try clicking cancel — but, of course, the cancel operation hangs too.
This costs thousands of dollars. Thousands! The usability is less grievous than SourceSafe (and that’s not saying much) — but the reliability, at least in my experience here, is worse. Fancy that.
I miss my Subversion.
December 4th, 2006 at 1:17 am
Perforce rules. Subversion is the poor man’s version of Perforce so if you liked svn you will love p4
December 4th, 2006 at 3:15 am
That does seem to be the consensus among people who have used Perforce for real.
But I tend to be distrustful of blanket statements presented completely free of concrete arguments ;-) … so help me out here: what specifically makes Subversion “the poor man’s version” other than the fact that it’s free? :-)
I did try out Perforce. Sure, they say it’s robust, but … it wanted me to ask it politely for permission before touching any file. What the … ? And just like the Team Foundation I’m wailing about in this blog, working offline was a bummer — want to review your changes? Tough. Revert them? Tough. And then you have to “correct” the “inconsistencies” with the server when you get back online, and “build a changelist after the fact.” In Subversion, changelists are after-the-fact by design, and you just get bugged less.
After the comfort of working with CVS and Subversion, these usability issues made Perforce less than tempting to me. Your mileage, evidently, varies :-) … so I am interested to hear exactly what places Perforce a cut above Subversion in your mind.