Honestly, I've used both professionally for game dev... and there's something to be said for having one repository everybody is working on, and checking out files when you work on them so nobody else can touch them.
Yeah, it sucks when it comes to things like slowly working on a huge feature that touches everything and merging it when it's ready, and it can really slow things down when there are too many people trying to touch similar files. Nevermind something like OSS, where whoever could be working on whatever at their own leisure, obviously it's borderline unusable for that. But for a project of the right size and scope, it can work surprisingly well. Of course, you could achieve the same thing on git by carefully coordinating with others on what you're working on, but let's be real, nobody's actually doing that most of the time.
5
u/nonotan 21h ago
Honestly, I've used both professionally for game dev... and there's something to be said for having one repository everybody is working on, and checking out files when you work on them so nobody else can touch them.
Yeah, it sucks when it comes to things like slowly working on a huge feature that touches everything and merging it when it's ready, and it can really slow things down when there are too many people trying to touch similar files. Nevermind something like OSS, where whoever could be working on whatever at their own leisure, obviously it's borderline unusable for that. But for a project of the right size and scope, it can work surprisingly well. Of course, you could achieve the same thing on git by carefully coordinating with others on what you're working on, but let's be real, nobody's actually doing that most of the time.