Who we are

We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.

If you want to give it a try, download it from here.

We also code SemanticMerge, and the gmaster Git client.

Clearcase users out there?

Sunday, October 01, 2006 Pablo Santos 4 Comments

Well, last week I had the opportunity to make some tests with Clearcase. No doubts Clearcase is one of the most powerful SCM tools out there. But I guess every system has its drawbacks... and Clearcase can't be an exception...

So, if you are a hardcore Clearcase user... lucky you!! You are not limited by many other tool's limits but... you will appreciate the following...

What is shown here is a simple three way merge scenario, and you will watch a quite subtle detail. First have a look at Clearcase handling the situation.

And now let's have a look at how Plastic SCM merge tool handles the same situation...

Can you see the difference? If you don't see it maybe you are already very used to SCM tools.

The problem (we also had it previously) is that the brackets are wrongly identified in Clearcase. It "thinks" the new methods are added "between" the original function (the base), while Plastic places the changes correctly...
Pablo Santos
I'm the CTO and Founder at Códice.
I've been leading Plastic SCM since 2005. My passion is helping teams work better through version control.
I had the opportunity to see teams from many different industries at work while I helped them improving their version control practices.
I really enjoy teaching (I've been a University professor for 6+ years) and sharing my experience in talks and articles.
And I love simple code. You can reach me at @psluaces.


  1. This is very good comparison!!

  2. Do you guys also use a 'config spec' to determine the snapshot view? (I'm assuming you don't support the concept of dynamic views)

  3. Yes, we don't support (yet) dynamic workspaces.

    What we currently have are workspaces (you can think on workspaces as snapshot views). And to actually configure a workspace, we do use "selectors".

    How does a selector look like? Well, have a look at the selector I'm currently using (we use Plastic to manage our own development)

    repository "codice"

    path "/01nerva/doc"
    br "/main/SCM0841"
    co "/main/SCM0841"

    path "/"
    br "/main"

    Meaning for subdirectory /01nerva/doc I'm working on branch /main/SCM0841 but for the rest I'm just looking into main (not checking out).

  4. Thanks Pablo that's cool. I see the simularity between 'selector' and 'config spec'. Looking forward to trying your 30-day trial.