4 ms·

I like Perforce. It may not be perfect. But it's idiot proof. "Days since gitastrophe" is a common phrase. There is no Perforce equivalent. You can't blow your

I like Perforce. It may not be perfect. But it's idiot proof. "Days since gitastrophe" is a common phrase. There is no Perforce equivalent. You can't blow your leg off. There aren't thousands of "Perforce made easy" blog posts because it's actually easy. There are no "fixing my p4 repo" tales because it never breaks. Thanks Perforce.

taesis 10y ago
In my personal experience, life (or, er, people) tend(s) to find a way to mess up any sufficiently complex, shared resource. In other words, I'm happy that it never breaks for you :3 Re. Perforce made easy, I'd suggest hitting up stack overflow or the p4 forums -- the community is much smaller than git's (i.e. practically the entire open source community vs. game developers), so there are fewer people available to write such blog posts (but enough to complain, evidently). I have a number of company internal-blog posts that explain Perforce to fellow newbs, but they can't be made public due to contracts and etc.
reitanqild 10y ago
Sorry for ruining the party (seriously). I like Perforce. It may not be perfect. But it's idiot proof. That's because it is almost impossible to do anything, good or bad with it. ;-) "Days since gitastrophe" is a common phrase. Never heard it before. There is no Perforce equivalent. You can't blow your leg off. The equivalent of a hand saw: you will have a harder time cutting off your leg with a hand saw than with a chain saw. There aren't thousands of "Perforce made easy" blog posts because it's actually easy. There are no "fixing my p4 repo" tales because it never breaks. Or because nobody uses it and those who do keeps the knowledge for themselves;-) Seriously: I used perforce for 18 months and I tried to understand why people loved it but no luck. Git isn't exactly perfect but compared to "checking out" a file before even editing it or not being able to commit without access to the server (IIRC) git is perfect. Oh, and not being able to check out a file that someone else has checked out, so if a dev goes on holiday without "checking in" the files first then you have to hack a bit to get ready for work again. The best argument however for git is that even the perforce guys have integrated with it. Thanks Perforce.
- forrestthewoods 10y ago
  Game development is probably >95% Perforce. Has been for over a decade. Will be for the next decade.
- AstralStorm 10y ago
  Bonus points when you get conflicts or try to use their terrible Swarm review system which relies on shelves. Also branching which hides previous history before branch out for no reason. No real branch merge functionality. Automatic merge being inferior to what Git has. And more...
deleted 10y ago
[deleted]
Diederich 10y ago
I worked at a company that used Perforce for a few years. We never used the p4 command-line tool because over the years people had written wrappers around all of the sub-commands to make things easier. The wrapper command-line tool was about 10,000 lines of Perl, and called 'p5'. Good times.

taesis 10y ago

In my personal experience, life (or, er, people) tend(s) to find a way to mess up any sufficiently complex, shared resource. In other words, I'm happy that it never breaks for you :3 Re. Perforce made easy, I'd suggest hitting up stack overflow or the p4 forums -- the community is much smaller than git's (i.e. practically the entire open source community vs. game developers), so there are fewer people available to write such blog posts (but enough to complain, evidently). I have a number of company internal-blog posts that explain Perforce to fellow newbs, but they can't be made public due to contracts and etc.

reitanqild 10y ago

Sorry for ruining the party (seriously). I like Perforce. It may not be perfect. But it's idiot proof. That's because it is almost impossible to do anything, good or bad with it. ;-) "Days since gitastrophe" is a common phrase. Never heard it before. There is no Perforce equivalent. You can't blow your leg off. The equivalent of a hand saw: you will have a harder time cutting off your leg with a hand saw than with a chain saw. There aren't thousands of "Perforce made easy" blog posts because it's actually easy. There are no "fixing my p4 repo" tales because it never breaks. Or because nobody uses it and those who do keeps the knowledge for themselves;-) Seriously: I used perforce for 18 months and I tried to understand why people loved it but no luck. Git isn't exactly perfect but compared to "checking out" a file before even editing it or not being able to commit without access to the server (IIRC) git is perfect. Oh, and not being able to check out a file that someone else has checked out, so if a dev goes on holiday without "checking in" the files first then you have to hack a bit to get ready for work again. The best argument however for git is that even the perforce guys have integrated with it. Thanks Perforce.

forrestthewoods 10y ago
Game development is probably >95% Perforce. Has been for over a decade. Will be for the next decade.
AstralStorm 10y ago
Bonus points when you get conflicts or try to use their terrible Swarm review system which relies on shelves. Also branching which hides previous history before branch out for no reason. No real branch merge functionality. Automatic merge being inferior to what Git has. And more...

deleted 10y ago

[deleted]

Diederich 10y ago

I worked at a company that used Perforce for a few years. We never used the p4 command-line tool because over the years people had written wrappers around all of the sub-commands to make things easier. The wrapper command-line tool was about 10,000 lines of Perl, and called 'p5'. Good times.