NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
several minutes ago. We don't need no stinkin' tactical nukes.
(By the way, do you have change for 10 million people?) --lwall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
VSS (Score:1)
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: (Score:1)
Visual SourceSafe Version Control: Unsafe at any Speed? [developsense.com] A mind-boggling list.
Re:VSS (Score:1)
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!
Reply to This
Parent
Re: (Score:1)
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.