4 ms·
Perforce is still in use in content heavy industries because Git still struggles with large binaries. Something with git branch semantics that could handle thos
by enjo 7y ago
Perforce is still in use in content heavy industries because Git still struggles with large binaries. Something with git branch semantics that could handle those files would be huge.
- emodendroket 7y agoIsn't that what Git LFS is about?
- sergiotapia 7y agoThis is funny, this exact same conversation happens on hn at least once a month. Reply for reply same convo
- Aeolun 7y agoYeah, but it’s not really out of the box.
- m463 7y agoI actually like perforce. (if you're not constrained by distributed) It does huge well, and I like the one-number changelist.
- jayd16 7y agoI really miss being able to check in chunks instead of full files, and streams are a poor replacement for git branches but it does let you do monorepo. P4V is a buggy mess though.
- reggieband 7y agoAnother feature of Perforce I liked was view specs. If your dealing with massive repos (as for example games tend to have) you often only want some small portion of the entire repo. You may also want to alter the repo layout on your local machine and a client view spec can allow you to slice and dice the content in many interesting ways. This is also very useful for working with external contractors. Not only can a user specify their own view specs, there is admin control for client views that can make portions of the repo read-only or effectively invisible on a per-user basis. Perhaps this is possible with git?