I think you're basically right here, but many companies are going to have a huge amount of code, builds, work history, etc wrapped up in these systems. So makin

I think you're basically right here, but many companies are going to have a huge amount of code, builds, work history, etc wrapped up in these systems. So making a big bang move off to a different system can be time consuming, costly, etc. I get why you might want to bridge the gap here or even stick with the other aspects of these systems while abandoning the vcs portion for git in that circumstance. Also sounds like gitswarm let's you integrate code back into a broader perforce codebase so you could see how in a huge org with hundreds of devs you could move your groups code into a git workflow without having to turn the whole battleship. So I think this solves some problems pragmatically for big teams already entrenched in perforce, but its not ideal.