20 engineers on Hacker News describe using Perforce first-hand: 5 endorse it, 7 regret it, 0 are mixed.
“Later, we moved to Perforce, which is good for larger binary files.”
endorse · production · kevin42 · 2024-04-16 · source ↗ · wrong label?“I've managed local servers with Git and Perforce on them, and it's a pain.”
regret · production · ChrisMarshallNY · 2023-10-23 · source ↗ · wrong label?“I was once responsible for doing this with a Perforce server. Only time in my career a VCS has lost data... it was shitty to deal with at the time.”
regret · production · KerrAvon · 2023-07-23 · source ↗ · wrong label?“we switched from Perforce or whatever the old centralized system was to gitfs and productivity tripled.”
regret · production · kungato · 2020-08-31 · source ↗ · wrong label?“whose only real feature beyond what Subversion offers is that they cost lots of money”
regret · production · groovy2shoes · 2016-10-19 · source ↗ · wrong label?“I've long said I'd love to see something that's as nice a GUI as p4v, but with git under the hood.”
endorse · production · dahart · 2016-10-02 · source ↗ · wrong label?“I worked at one company where you couldn't even create a branch or do a merge without going through one of them! Perforce. Never again.”
regret · production · icedchai · 2015-08-10 · source ↗ · wrong label?“The short answer is that we run perforce... We've reaped a number of benefits as a result.”
endorse · production · zaphar · 2014-01-08 · source ↗ · wrong label?“Things I have become an expert in that are now useless to me and probably not valued by an employer”
regret · production · pkteison · 2013-10-07 · source ↗ · wrong label?“You are correct that one monolithic Perforce repo is a bit of a pain point, but that doesn't necessarily mean that the right decision is to shatter our codebase”
regret · production · EricBurnett · 2012-02-03 · source ↗ · wrong label?“I've generally enjoyed Perforce, but for our SCM needs at the time SVN more then suited our build and deployment strategies.”
endorse · production · mey · 2011-11-02 · source ↗ · wrong label?“Once we moved to P4 it was a relief, and still is.”
endorse · production · malkia · 2010-02-17 · source ↗ · wrong label?“We have a 20 year old code base we migrated from Perforce to svn about 10 years ago.”
neutral · production · thewebcount · 2020-03-08 · source ↗ · wrong label?“or just checking vs projects into perforce manually, I'd pick any of those before bazel”
neutral · production · bobdobbs666 · 2019-12-23 · source ↗ · wrong label?“What we did in games before git was everyone pushed to master at all times (or whatever they called it in Perforce”
neutral · production · dahart · 2017-10-02 · source ↗ · wrong label?“I suggested that we try out the desktop version of Git to make transition from p4 easier.”
neutral · production · thinkaboutit113 · 2017-05-03 · source ↗ · wrong label?“I suggested that we try out the desktop version of Git to make transition from p4 easier.”
neutral · production · thinkaboutit113 · 2017-05-03 · source ↗ · wrong label?“It's far and away the most useful tool I have outside of the IDE (particularly since we use Perforce).”
neutral · production · FeloniousHam · 2013-12-05 · source ↗ · wrong label?“Ive been using perforce/p4 since 97. the last 8 years have been coupled with P4V and the eclipse plugins.”
neutral · production · 8 yr · MikeTLive · 2013-11-18 · source ↗ · wrong label?“We use Perforce and VC++ .slns, sometimes with apps split into DLLs”
neutral · production · TwoBit · 2011-12-19 · source ↗ · wrong label?