Git vs. Plastic SCM

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Git
Score 10.0 out of 10
N/A
N/AN/A
Plastic SCM
Score 8.2 out of 10
Enterprise companies (1,001+ employees)
Plastic SCM is a full stack version control system that aims to make software configuration easy. It focuses on enabling dev teams get work done by facilitating branching, diffing and merging. The vendor says that for those purposes it provides cross-platform apps and GUIs with: Branch explorer Diffing and merging tools (both syntactic and semantic) On-premises and cloud repo management Code review mergebots (last mile…
$6.95
per user
Pricing
GitPlastic SCM
Editions & Modules
No answers on this topic
Cloud Edition
$6.95
per user
Team Edition (on prem)
$9.95
per user
Enterprise Edition
$23.25
per user
Enterprise Edition (perpetual)
$595.00
per user
Offerings
Pricing Offerings
GitPlastic SCM
Free Trial
NoYes
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeOptional
Additional Details* Educational institutions receive a substantial discount on Plastic SCM licensing fees * Corporate/volume pricing is available * For more information, please contact sales at sales@codicesoftware.com
More Pricing Information
Community Pulse
GitPlastic SCM
Considered Both Products
Git
Chose Git
Git is by far the best version control system out there. It's open source, free, and fast. No other version control system I've ever used has had all three features.
Plastic SCM

No answer on this topic

Top Pros
Top Cons
Best Alternatives
GitPlastic SCM
Small Businesses
GitHub
GitHub
Score 9.1 out of 10
Salt
Salt
Score 7.8 out of 10
Medium-sized Companies
GitHub
GitHub
Score 9.1 out of 10
Salt
Salt
Score 7.8 out of 10
Enterprises
Perforce Helix Core
Perforce Helix Core
Score 6.3 out of 10
Perforce Helix Core
Perforce Helix Core
Score 6.3 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
GitPlastic SCM
Likelihood to Recommend
10.0
(36 ratings)
8.4
(3 ratings)
Likelihood to Renew
10.0
(1 ratings)
-
(0 ratings)
Usability
9.0
(1 ratings)
-
(0 ratings)
Support Rating
8.5
(11 ratings)
-
(0 ratings)
Implementation Rating
9.0
(1 ratings)
-
(0 ratings)
User Testimonials
GitPlastic SCM
Likelihood to Recommend
Open Source
GIT is good to be used for faster and high availability operations during code release cycle. Git provides a complete replica of the repository on the developer's local system which is why every developer will have complete repository available for quick access on his system and they can merge the specific branches that they have worked on back to the centralized repository. The limitations with GIT are seen when checking in large files.
Read full review
Plastic SCM
Plastic SCM is well suited for the distributed development environment, where branching and merging can easily be handled. Its a good tool for version controlling, especially for a big team which is contributing to a big project simultaneously. Situation where Plastic SCM is not at all well suited are : If the project is smaller one and need to be handled by couple of people. So in that case setting up Plastic SCM and educating people to work on it is not at all efficient
Read full review
Pros
Open Source
  • Ability to create branches off current releases to modify code that can be tested in a separate environment.
  • Each developer had their own local copy of branches so it minimizes mistakes being made.
  • Has a user-friendly UI called Git Gui that users can use if they do not like using the command line.
  • Conflicts are displayed nicely so that developers can resolve with ease.
Read full review
Plastic SCM
  • Version Control
  • Organizing Workflow
  • Transparency
Read full review
Cons
Open Source
  • There can be quite a number of commands once you get to the advanced features and functionality of Git. Takes time to master.
  • Doesn't handle static assets (ie: videos, images, etc.) well. Although in the recent years, new functionality has been introduced to address this.
  • Many different GUIs, many people (including myself) opt to just use the command-line.
Read full review
Plastic SCM
  • Interface
  • Documentation
  • Learning curve
  • Unity integration
Read full review
Likelihood to Renew
Open Source
Git has met all standards for a source control tool and even exceeded those standards. Git is so integrated with our work that I can't imagine a day without it.
Read full review
Plastic SCM
No answers on this topic
Usability
Open Source
Git is easy to use most of the time. You mostly use a few commands like commiting, fetch/pull, and push which will get you by for most of time.
Read full review
Plastic SCM
No answers on this topic
Support Rating
Open Source
I am not sure what the official Git support channels are like as I have never needed to use any official support. Because Git is so popular among all developers now, it is pretty easy to find the answer to almost any Git question with a quick Google search. I've never had trouble finding what I'm looking for.
Read full review
Plastic SCM
No answers on this topic
Implementation Rating
Open Source
It's easy to set up and get going.
Read full review
Plastic SCM
No answers on this topic
Alternatives Considered
Open Source
I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different.
The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in a location you can't reach (behind a VPN, intranet - etc), you cannot commit. If you want to make a copy of your code, you have to literally copy/paste it. With Git, you do not have this problem. Your local copy is a repository, and you can commit to it and get all benefits of source control. When you regain connectivity to the main repository, you can commit against it. Another thing for consideration is that Git tracks content rather than files. Branches are lightweight and merging is easy, and I mean really easy.
It's distributed, basically every repository is a branch. It's much easier to develop concurrently and collaboratively than with Subversion, in my opinion. It also makes offline development possible. It doesn't impose any workflow, as seen on the above linked website, there are many workflows possible with Git. A Subversion-style workflow is easily mimicked.
Read full review
Plastic SCM
Plastic has best integration with unity - zero issues, native, straightforward. GitHub feels more stable but for smaller and or indie teams plastic s version control feels much more under control - you click, you feel safe. moreover, there is no need for extra tools such as gitkraken, gitlab, Sourcetree, fork, etc. it is really easy to develop games this way.
Read full review
Return on Investment
Open Source
  • Git has saved our organization countless hours having to manually trace code to a breaking change or manage conflicting changes. It has no equal when it comes to scalability or manageability.
  • Git has allowed our engineering team to build code reviews into its workflow by preventing a developer from approving or merging in their own code; instead, all proposed changes are reviewed by another engineer to assess the impact of the code and whether or not it should be merged in first. This greatly reduces the likelihood of breaking changes getting into production.
  • Git has at times created some confusion among developers about what to do if they accidentally commit a change they decide later they want to roll back. There are multiple ways to address this problem and the best available option may not be obvious in all cases.
Read full review
Plastic SCM
  • Easy to use
  • Cheap
  • Better than git for us
  • Artists love it
Read full review
ScreenShots

Plastic SCM Screenshots

Screenshot of Screenshot of Screenshot of Screenshot of Screenshot of Screenshot of