Stage 1:
cp somefile.pl{,.bak}
Stage 2:
cvs mv^W^W
What do you mean I can't rename files? No, I don't give a damn if you can hack the attic to preserve history. (then the real fight starts)
Stage 3:Who the **** has locked that file in VSS? What do you mean they're on vacation? Where's the damned administrator?
Stage 4:svn mv this that svn commit this that -m "Take that, CVS!" svn merge -r9535:HEAD http://10.1.1.118/svn/pips3/trunk/ .
What do you mean subversion has lost track of those damned files again? I just did an svn mv and now it's telling me it doesn't exist in source control ... until I try to add it. And the merge just added a bunch of files but now tells me they're not in source control? WTF?
Stage 5:git init .
Looks good so far ...
And the saga continues.
Welcome to the fold! The terrors of times past will soon be a distant memory.
The start will be somewhat bumpy, though, as git breaks with a number of assumptions you may have carried along – even compared to other DVCSs, it has a few unique features. But I wouldn’t want to trade them back in. The index is the most initially confusing, and it makes such perfect sense to me now that I miss it elsewhere.
It's pretty telling of the quality of a product when it's own developers don't use it.
Like many others, we choose to call it Visual SourceUnSafe, but must use it because it's the system that works best with Powerbuilder, sadly. At least I can use something else for our web products....
If you only occasionally had to swear at VSS, consider yourself lucky!
Re:VSS
Aristotle on 2008-07-02T03:16:56
Visual SourceSafe Version Control: Unsafe at any Speed? A mind-boggling list.
Re:VSS
jplindstrom on 2008-07-02T15:51:30
It is a sad, sad excuse for a source control system.
We used it at my last job for years, all the while know it was shit and meaning to switch to something else.
And in one of the most moronic moves in that company (the other being hiring Accenture), we switched to... Telelogic Synergy.
That, Ladies and Gentlemen, is SourceSafe done wrong on an Enterprise(tm) level.
Completely useless in so many, many ways, all in the name of an "audit trail" and "integration" with equally inept systems for requirements and such.
If they claim they have "reference customers", actually call them up and talk to the people using the system. Not(!) the build managers, or the people who brought it in, but the programmers actually forced to use it every day.
Or, in short: stay away!
Re:VSS
CromeDome on 2008-07-02T17:48:45
We're actually looking at SourceGear. Compatible with VSS, (seemingly) none of the pitfalls. Curious to know if it works the same way with PB though. Only gripe with SourceGear, so far, is the price for the amount of developers we have.
Re: PowerBuilder
jplindstrom on 2008-07-02T15:43:17
How do you like PowerBuilder? I've heard good things about it, and that was many many years ago.
Re: PowerBuilder
CromeDome on 2008-07-02T17:50:58
It's nice, mostly
;) Like most development tools, there's a laundry list of oddities you have to code around, but it's mature, stable, and easy to pick up. I have never seen a faster way to put together a data-driven GUI app. It's easy enough that our non-programmers can make report changes, too. Highly recommend it if you want to do GUI apps on windows and not use Visual Studio.