4 ms·
We loooooooooove Perforce in the games industry because it handles repositories with hundreds of gigabytes of binary data better than most (if not all) other so
by maximilianburke 11y ago
We loooooooooove Perforce in the games industry because it handles repositories with hundreds of gigabytes of binary data better than most (if not all) other source control systems. It's fast, reliable, and space efficient on the client.
The DVCS features in the new versions of Perforce plug the holes where a lighter weight solution is desired, and have also been allowing us to more seamlessly mirror projects across previously separate servers.
- tenfingers 11y agoIs 'looooooooooove' ironic? I've used p4 for several years, and even though I now basically only use git, I still think it's one of the best thought-of and implemented SCM systems out there [disclaimer: never used bitkeeper]. It's simple, elegant, compact and well performing in any scenario. You don't need a "perforce from the group up" tutorial to understand how it works. p4v is awesome for history navigation: no git frontent comes even close. Shallow repositories somehow mitigate git issues for large repositories, even though it isn't convenient. Over time I came to appreciate some advanced manipulation commands in git so I don't think I'll ever switch back, but I hope Perforce will continue to go strong, as it's a very solid product.
- yo-code-sucks 11y agoYeah, fuck simplicity, let's clobber and merge every fucking thing.
- maximilianburke 11y agoNo, not ironic or sarcastic at all! It really is wonderful. We're starting to scale up our edge/commit server network in order to have teams iterate on 100+GB repositories across five+ locations in North America and Europe and it mostly just works.