Information Required

[Angel Ezquerra]

On Thu, Jan 15, 2015 at 7:44 AM, Dirk Heinrichs <dhs at recommind.com> wrote:

>
> Am 14.01.2015 um 20:49 schrieb Angel Ezquerra:
>
>  One last piece of advice: under no circumstances choose a tool called
> ClearCase
>
>
> Did you ever use it yourself? If I had the choice, I'd always favour CC.
> No other (D)VCS, free or proprietary, comes close to its capabilities,
> especially when it comes down to building your software reliably. Of
> course, it's quite expensive and has somewhat higher HW requirements than
> other tools. So, if you don't want to spend the money, your next best
> choices are of course Mercurial or Git ;) .
>
> Bye...
>

Unfortunately I've had to use Clear-Case for many, many years. In fact at
some point I even made a small custom clear-case GUI to complement the one
that was provided by Rational. Over the years I've used a pretty vanilla
Clear-Case installation, another with some custom scripting layer on top to
force a particular development workflow and another based on the UCM
workflow. They all were really terrible.

It is actually hard to choose where to start when criticizing Clear-Case.
There are so many wrong things about it! From its slowness, to its
out-dated model, to its incredibly clunky windows client, to how hard it
makes it to go back to older versions of your source code, to the
brittleness of config-specs, to the lack of any advanced history editing
features, to the huge need of administration infrastructure and overhead...
I could go on. I honestrly think that I would refuse a doubling of my
salary if I required me to use Clear-Case again.

I am actually very surprised. You are the very first person that I've ever
known to prefer Clear-Case to mercurial or git (and which had used these
newer systems). I guess that, as the saying goes, to each its own...

Cheers,

Angel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20150115/dbfa446a/attachment-0002.html>