IBM DevOps Code ClearCase vs. Plastic SCM vs. Microsoft Visual SourceSafe (Discontinued)

IBM Rational ClearCase might be better suited for a smaller / simpler code base. Larger code bases really slow it down... but then again there are better alternatives out there for source control

Incentivized

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

I would not recommend Visual SourceSafe to anyone out there as there are so many better, more modern solutions that do what it does and much more. Visual SourceSafe should be retired in most cases.

• Rational ClearCase is excellent for handling versioning and branching. No other tool I've used has the depth that ClearCase has when it comes to handling complex branching scenarios and identifying where certain versions of particular files are within a particular configuration.
• Rational ClearCase handles parallel development of many dependent applications really well.
• The use of ClearCase Views to switch between projects and configurations is extremely convenient as opposed to the local workstation model of the competitors.

Incentivized

• Version Control
• Organizing Workflow
• Transparency

Incentivized

• At this point in its lifecycle there are not many things VSS does well
• Its main strength would be its ability to be self contained on a local drive
• It is a basic Code repository

Incentivized

• Extremely buggy.
• Sometimes the repository gets locked for no reason.
• Slow.

Incentivized

• Interface
• Documentation
• Learning curve
• Unity integration

Incentivized

• The system stability could be improved. Often we get file corrupted errors.
• The User Interface is not modern and not user-friendly.
• Concurrent check-outs could be added, allowing more people to work on the same file at the same time.
• Add conflict resolution, files comparison, blame file, features that any modern source control program should have.

Incentivized

The current status of Visual SourceSafe is not usable. There are many things that are just so out of the date that it should be retired and not looked at any longer. If you have an existing application that is stored in it, I'd consider migrating it to a modern tool.

It's a Microsoft product so the customer support is great. The program has been around a long time so there are plenty of places on line to get assistance. Also almost any development shop you go to will have at least one developer who has used this product extensively in their career.

Incentivized

If development is centrallized to one location and your company releases hundreds of customized versions of your software per year, then ClearCase is the best tool for managing the complexity of multiple versions of customized software. If your company has globally distributed development, then I'd recommend Team Foundation Server over ClearCase. If your organization uses Agile Methodologies, then I'd recommend TFS with GIT.

Incentivized

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.

Incentivized

Incentivized

• Managed code versioning for many years.
• Only one person can edit code at a time - slows processing down.
• IBM is an expensive product to support.

Incentivized

• Easy to use
• Cheap
• Better than git for us
• Artists love it

Incentivized

• When we started using it, it allowed us to do source code versioning and store the code in a centralized location and not locally.
• We are using it for very few projects with few developers that still maintain those applications and do not have time to merge the source code to Git.

Incentivized