So, is it possible to deal with Perforce marking files read-only? -- Yes. And it's not complicated, but the whole idea that that how the system should work is stupid. The problem is, however, exceptionally common. In my days working with Perforce there hadn't been a day when this problem didn't rear its ugly head.

So, maybe Perforce is scoring better on some metric, but in the day-to-day it generates so much hatred towards itself that I don't care if it can handle big files better than Git does. I only need to handle big files maybe a few times a year. And I prefer to get frustrated only twice or three times a year than to be fuming every time I have to touch files in my project.

A good git gui works as well as p4v (and usually far less buggy).

The major difference in my eyes is that p4 can enforce more settings from the server. It's easier to get artists set up in p4 than git.

> There's a reason that like 105% of AAA game dev uses Perforce.

Irony of ironies, Unreal is distributed with git but largely uses p4.

P4 is dominant but I feel like a lot of that is momentum. Making a Unity game with git is pretty easy. Some Unreal tooling is built around p4 only but not really for any technical reasons.