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

Git

137.1K
112.5K
+ 1
6.6K
Plastic SCM

30
57
+ 1
16
Add tool

Git vs Plastic SCM: What are the differences?

What is Git? Fast, scalable, distributed revision control system. 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.

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..

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

"Distributed version control system" is the top reason why over 1441 developers like Git, while over 6 developers mention "Wanna do Branch per Task Dev? Plastic rocks it" as the leading cause for choosing Plastic SCM.

Git is an open source tool with 27.9K GitHub stars and 16.1K GitHub forks. Here's a link to Git's open source repository on GitHub.

Decisions about Git and Plastic SCM
Kamaldeep Singh

SVN is much simpler than git for the simple stuff (checking in files and updating them when everyone's online), and much more complex than git for the complicated stuff (branching and merging). Or put another way, git's learning curve is steep up front, and then increases moderately as you do weird things; SVN's learning curve is very shallow up front and then increases rapidly.

If you're storing large files, if you're not branching, if you're not storing source code, and if your team is happy with SVN and the workflow you have, I'd say you should stay on SVN.

If you're writing source code with a relatively modern development practice (developers doing local builds and tests, pre-commit code reviews, preferably automated testing, preferably some amount of open-source code), you should move to git for two reasons: first, this style of working inherently requires frequent branching and merging, and second, your ability to interact with outside projects is easier if you're all comfortable with git instead of snapshotting the outside project into SVN.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Git
Pros of Plastic SCM
  • 1.4K
    Distributed version control system
  • 1.1K
    Efficient branching and merging
  • 964
    Fast
  • 846
    Open source
  • 728
    Better than svn
  • 368
    Great command-line application
  • 306
    Simple
  • 291
    Free
  • 232
    Easy to use
  • 222
    Does not require server
  • 27
    Distributed
  • 22
    Small & Fast
  • 18
    Feature based workflow
  • 15
    Staging Area
  • 13
    Most wide-spread VSC
  • 11
    Disposable Experimentation
  • 11
    Role-based codelines
  • 7
    Frictionless Context Switching
  • 6
    Data Assurance
  • 5
    Efficient
  • 4
    Just awesome
  • 3
    Github integration
  • 3
    Easy branching and merging
  • 2
    Compatible
  • 2
    Possible to lose history and commits
  • 2
    Flexible
  • 1
    Team Integration
  • 1
    Easy
  • 1
    Light
  • 1
    Fast, scalable, distributed revision control system
  • 1
    Rebase supported natively; reflog; access to plumbing
  • 1
    Flexible, easy, Safe, and fast
  • 1
    CLI is great, but the GUI tools are awesome
  • 1
    It's what you do
  • 0
    Phinx
  • 8
    Wanna do Branch per Task Dev? Plastic rocks it
  • 3
    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 Git
Cons of Plastic SCM
  • 16
    Hard to learn
  • 11
    Inconsistent command line interface
  • 9
    Easy to lose uncommitted work
  • 7
    Worst documentation ever possibly made
  • 5
    Awful merge handling
  • 3
    Unexistent preventive security flows
  • 3
    Rebase hell
  • 2
    When --force is disabled, cannot rebase
  • 2
    Ironically even die-hard supporters screw up badly
  • 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 companies use Git?
What companies use Plastic SCM?
See which teams inside your own company are using Git or Plastic SCM.
Sign up for Private StackShareLearn More

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

What tools integrate with Git?
What tools integrate with Plastic SCM?

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

What are some alternatives to Git and Plastic SCM?
GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.
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.
Bitbucket
Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users.
Perforce
Visibility, access control, workflow and code management for Git environments. Flexibility of collaborating on the same codebase and code reviews using any combination of Perforce and Git workflows and tools without compromise.
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.
See all alternatives