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.
Plastic SCM is a tool in the Version Control System category of a tech stack.
Visual Studio Code, Jenkins, Visual Studio, TeamCity, and Gluon are some of the popular tools that integrate with Plastic SCM. Here's a list of all 5 tools that integrate with Plastic SCM.
Here’s a list of reasons why companies and developers use Plastic SCM.
Here are some stack decisions and reviews by companies and developers who chose Plastic SCM in their tech stack.
I use Plastic SCM because I can handle, via Gluon, non-text or non-code assets in the same repo as the programmers I work with, regardless of the size, if I have to lock those or files or anything. It is a point and click interface that keeps version control for me in the background will keeping me away from all its complexities. It's the perfect #VersionControlSystem to do distributed or centralized version control when you don't like any of those.
Plastic SCM is built using .NET, C# and Mono. In Product we decided to go for Amplitude and Segment to track usage and monitor activation as well as Intercom to communicate news, updates and tips. The reasons to pick all of those are pretty similar: scalability and ease of use.