That thread looks so far out of date that it’s irrelevant.
Last month one of my colleagues lost three months of work to a poorly designed Perforce gotcha. It’s a bit idealistic to say that Git is hell and Perforce is the best when what I suspect is actually the case with that conclusion is just lack of knowledge about both systems. Git is better point by point and all-round and Perforce is just a simpler, less good system. But any version control is better than none (until you lose your Perforce repo keys haha).
Edit: the more I read of that thread you linked the more “a little knowledge is more dangerous than none at all” starts to apply. That guy doesn’t know what he’s talking about:
If you’re doing per-file commits with file locking you might as well all use a Dropbox share. Anyone who says the above has exactly zero experience with Git or large teams.
Git is designed to be robust and easy to use while elegantly merging entire branches of code together at-will. There isn’t a single feature in Perforce that Git doesn’t have covered, including file-locking. It’s free and it’s used by the best software developers in the industry (which might be why Epic don’t use it internally 
)