23 messages in com.perforce.perforce-user[p4] RE: ClearCase (again)
FromSent OnAttachments
Bala Subramanian02 May 2000 09:45 
Christophe MONJARET05 May 2000 08:59 
Plumlee, Philip08 May 2000 09:22 
Meyer, Maurice08 May 2000 10:09 
Jeff A. Bowles08 May 2000 10:38 
Plumlee, Philip08 May 2000 11:03 
Marc S. Gibian08 May 2000 12:08 
Steve Bennett08 May 2000 12:23 
Greg Spencer08 May 2000 12:24 
Dave Lewis08 May 2000 12:42 
Piaw Na08 May 2000 13:24 
Marc S. Gibian08 May 2000 13:41 
Piaw Na08 May 2000 14:03 
Marc S. Gibian08 May 2000 14:03 
Piaw Na08 May 2000 14:12 
Morton, Simon08 May 2000 14:12 
Plumlee, Philip08 May 2000 14:17 
Dave Lewis08 May 2000 14:17 
Richard Geiger08 May 2000 14:21 
Fredric Fredricson08 May 2000 14:27 
Marc S. Gibian08 May 2000 14:27 
Meyer, Maurice08 May 2000 15:26 
The Great Vobadmin09 May 2000 05:50 
Subject:[p4] RE: ClearCase (again)
From:Marc S. Gibian (mgib@amazon.com)
Date:05/08/2000 02:03:42 PM
List:com.perforce.perforce-user

I have to say that this is the first time I've heard *anyone* compare Clearcase favorably with Perforce. I've only heard nightmare stories about Clearcase. In fact, at my last job, 2 of the principal engineers once said that they would quit if Clearcase was ever introduced into the company. Needless to say, we picked Perforce. :-)

I wonder about any engineer that would quit over a tool choice, be it ClearCase, Perforce, VSS, SCCS, etc. Yes, we should have and contribute our expertise, and good tools do make us more productive, and we have a responsibility to make our point and hold our group, but we are engineers after all and do not need to be coddled. To paraphrase an old quote, real engineers don't need no stinkin high level language. Real engineers write BINARY (who needs compilers, assemblers, linkers, or symbolic debuggers).

Now at this company, I picked perforce because of the overwhelmingly good experience with it at my last job. Other engineers from my last job have also migrated to perforce as they joined new companies. My impression with Clearcase is that it can be a good system, if you have a couple of dedicated CM people. Startups (the companies that tend to use perforce) don't tend to have that much resources, and usually one of the engineers can administer perforce until the company gets big enough to afford a CM person.

I personally have setup and administered ClearCase installations of varying size as THE CM person in the team/company while also contributing as a principal engineer. It CAN be done without even one dedicated CM person. Maybe its just the qualifications of the person/people?

Note that I own Rational stock (I'm a former Pure Software employee). So if anyone had a financial incentive to bash perforce and tout Clearcase. But as an engineer, I can and have recommended perforce to lots of other engineers. I haven't met any other engineers who could say the same about Clearcase.

I own no stock or have any other interest that would benefit from the success of failure of any CM product, ClearCase or other, other than simply as a practicing principal software engineer. I should point out that I have been an outspoken participant in the ClearCase Users Group when using that tool and as critical of some aspects of that product as I have been of any other. Yet, when viewed in its entirety, I feel it provides a solution for CM that is more complete than any other. Even better, I really do find it useful out-of-the-box, without having to write wrappers, custom triggers, and other support pieces. The ONLY effort was determining "sane" configurations for each deployment. The rest just flowed and took care of itself. Honest. It really did. For a couple of years in the case of one installation.

-Marc