Need advice about which tool to choose?Ask the StackShare community!
Perforce vs Plastic SCM: What are the differences?
Perforce: Self-hosted Version Control Software. 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; 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..
Perforce and Plastic SCM are primarily classified as "Code Collaboration & Version Control" and "Version Control System" tools respectively.
"Great for Enterprise level use" is the primary reason why developers consider Perforce over the competitors, whereas "Wanna do Branch per Task Dev? Plastic rocks it" was stated as the key factor in picking Plastic SCM.
Pros of Perforce
- Powerful3
- Great for Enterprise level use3
- Robust2
- Scalable1
Pros of Plastic SCM
- Wanna do Branch per Task Dev? Plastic rocks it8
- No Size limite4
- File Locking2
- Simple, easy to use interfaces. Resilient and solid2
- Very fast1
Sign up to add or upvote prosMake informed product decisions
Cons of Perforce
Cons of Plastic SCM
- Always uses automatic conflict resolution first1
- Adds files with only changed timestamp to pending1
- Keyboard shortcuts are lacking1
- Can't place windows next to each other to save space1
- No dark theme1
- Doesn't have file staging1