Plastic SCM vs. Git

Plastic SCM (source control management) is Unity’s replacement for the Collaboration tool. Plastic SCM is a system for sharing work that’s integrated directly in the Unity interface.

Choosing Plastic SCM or Git really depends on the scope of your version control requirements, and personal preference.

My opinions regarding the advantages of Plastic SCM over Git are:

1) Simplified and streamlined workflow. Starting a new repo or connecting to an existing repo with Plastic SCM takes two clicks, and the Unity interface keeps you updated as you work:

2) Graphic visualization tools:

This to me is a really big plus. The Plastic SCM interface is laid out in a very easy to interpret intuitive format. If you’ve ever struggled to understand Git, Plastic SCM might just be heaven-sent. After spending hours and hours deciphering cryptic git commands, Plastic SCM is a huge relief. This alone is worth the switch for me.

3) No need to worry about lfs or exporting packages. If you’ve ever tried to share your project with a colleague or just between pc’s in different offices, you probable found out the hard way that the standard git ignore file leaves out a bunch of stuff. Plastic SCM can handle your entire project with ease.

Now the downside to Plastic SCM:

1) Plastic SCM access is limited to team members. If you want your code to be shared with the world, Git is the way to go.

2) Plastic SCM charges by the user for any team over 3 users. Cloud Edition is $7 per user per month, and Enterprise Edition is $23 per user per month.

3) No pretty analytics like GitHub provides:

Finally, if you want the best of both worlds, you can use Plastic SCM and Git simultaneously, and of course you can use GitHub Copilot without using Git.