Need advice about which tool to choose?Ask the StackShare community!

Mercurial

213
193
+ 1
106
Plastic SCM

33
68
+ 1
17
Add tool

Mercurial vs Plastic SCM: What are the differences?

What is Mercurial? A distributed version control system. Mercurial is dedicated to speed and efficiency with a sane user interface. It is written in Python. Mercurial's implementation and data structures are designed to be fast. You can generate diffs between revisions, or jump back in time within seconds.

What is Plastic SCM? A distributed version control with strong merging, great GUIs and support for huge files. Plastic SCM is a distributed version control designed for big projects It excels on branching and merging, graphical user interfaces, and can also deal with large files and even file-locking (great for game devs).

It includes "semantic" features like refactor detection to ease diffing complex refactors..

Mercurial and Plastic SCM can be primarily classified as "Version Control System" tools.

"Easy-to-grasp system with nice tools" is the primary reason why developers consider Mercurial over the competitors, whereas "Wanna do Branch per Task Dev? Plastic rocks it" was stated as the key factor in picking Plastic SCM.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Mercurial
Pros of Plastic SCM
  • 19
    A lot easier to extend than git
  • 17
    Easy-to-grasp system with nice tools
  • 13
    Works on windows natively without cygwin nonsense
  • 11
    Written in python
  • 9
    Free
  • 8
    Fast
  • 6
    Better than Git
  • 6
    Best GUI
  • 4
    Better than svn
  • 2
    Hg inc
  • 2
    Good user experience
  • 2
    TortoiseHg - Unified free gui for all platforms
  • 2
    Consistent UI
  • 2
    Easy-to-use
  • 2
    Native support to all platforms
  • 1
    Free to use
  • 8
    Wanna do Branch per Task Dev? Plastic rocks it
  • 4
    No Size limite
  • 2
    File Locking
  • 2
    Simple, easy to use interfaces. Resilient and solid
  • 1
    Very fast

Sign up to add or upvote prosMake informed product decisions

Cons of Mercurial
Cons of Plastic SCM
  • 0
    Track single upstream only
  • 0
    Does not distinguish between local and remote head
  • 1
    Always uses automatic conflict resolution first
  • 1
    Adds files with only changed timestamp to pending
  • 1
    Keyboard shortcuts are lacking
  • 1
    Can't place windows next to each other to save space
  • 1
    No dark theme
  • 1
    Doesn't have file staging

Sign up to add or upvote consMake informed product decisions

What is Mercurial?

Mercurial is dedicated to speed and efficiency with a sane user interface. It is written in Python. Mercurial's implementation and data structures are designed to be fast. You can generate diffs between revisions, or jump back in time within seconds.

What is Plastic SCM?

Plastic SCM is a distributed version control designed for big projects. It excels on branching and merging, graphical user interfaces, and can also deal with large files and even file-locking (great for game devs). It includes "semantic" features like refactor detection to ease diffing complex refactors.

Need advice about which tool to choose?Ask the StackShare community!

Jobs that mention Mercurial and Plastic SCM as a desired skillset
What companies use Mercurial?
What companies use Plastic SCM?
See which teams inside your own company are using Mercurial or Plastic SCM.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Mercurial?
What tools integrate with Plastic SCM?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

Mar 4 2020 at 5:14PM

Atlassian

GitBitbucketWindows+4
3
736
What are some alternatives to Mercurial and Plastic SCM?
Apache Storm
Apache Storm is a free and open source distributed realtime computation system. Storm makes it easy to reliably process unbounded streams of data, doing for realtime processing what Hadoop did for batch processing. Storm has many use cases: realtime analytics, online machine learning, continuous computation, distributed RPC, ETL, and more. Storm is fast: a benchmark clocked it at over a million tuples processed per second per node. It is scalable, fault-tolerant, guarantees your data will be processed, and is easy to set up and operate.
Git
Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
SVN (Subversion)
Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations.
DVC
It is an open-source Version Control System for data science and machine learning projects. It is designed to handle large files, data sets, machine learning models, and metrics as well as code.
Magit
It is an interface to the version control system Git, implemented as an Emacs package. It aspires to be a complete Git porcelain. While we cannot (yet) claim that it wraps and improves upon each and every Git command, it is complete enough to allow even experienced Git users to perform almost all of their daily version control tasks directly from within Emacs. While many fine Git clients exist, only deserve to be called porcelains.
See all alternatives