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.

Laws of Simplicity

Tuesday, August 28, 2012 Amalia 1 Comments

Lately, we have thinking about how to explain Plastic SCM as an Enterprise DVCS.
The latest article "Plastic SCM - DVCS at Enterprise Level" written by Pablo and published in InfoQ helped me. But I keep on reading, thinking, studying and writing about it. Recently I realized how important these actions are in my life.

How do I explain Plastic SCM in easy way?

I discovered "The Laws of Simplicity" by John Maeda. It was published in 2006.
The book is about his thoughts on simplicity. John Maeda explores how we can redefine the notion of "improved" so that it doesn't mean something added on.
So, why do not try to explain Plastic SCM through The Ten Laws of Simplicity?

Impossibly complex applications are the default deliverable for new programmers. Simplicity isn't achievable as a passive goal; it's a force that must be actively applied.
And Plastic SCM has it

1 comment:

  1. Isn't law 10 redundant?
    Isn't it included in law 1?

    A French author (Alain Berthoz, but I can see there are other attempts in similar directions...) noted that there is only one word for 'simple', but two for 'complicated' and 'complex'.
    He then coined 'simplex' as something like structured, or rather evolved simplicity, simplicity through evolution (and complexity).