Perforce Helix Core

“Perforce was way ahead of it's time, everyone still wants a monotonically increasing changelist identifier too.”

“I am about 80% certain that using well configured Perforce could work just as well while saving Anthropic some money”

“can amortize the cost over many customers so it should be cheaper and faster to reuse”

“It just had a terrible ui and didn’t allow me to code on the beach.”

“This is why you see continued use of centralized version control systems (e.g. Perforce, ClearCase) at organizations that need these things.”

“P4 is significantly better at centralized teams who work in the same physical office.”

“show that the tools can still improve drastically”

“P4 a) can handle big files just fine”

“P4 a) can handle big files just fine and b) you don't really care about the history of the entire repository”

“very flexible permissions system”

“i always thought the workspace mapping and workspace template model in p4 was pretty elegant”

“their software is buggy too.. i have no idea how this company can survive with what is, honestly, an unfinished product”

“Is Perforce good? Ehhh not really. It's been stagnant for 15 years.”

“You can literally ignore all of the concepts that P4 has and still muddle your way into getting things updated.”

“I prefer something like Perforce if someone can manage it for me, or it's a set-and-forget type situation”

“rather than use reconcile (because it's so slow)”

“For games you want centralized per file versioning, like Perforce.”

“It always feels like everyone's checkout is a unique blend of local files and permissions you have to fix up now and then.”

“learning to use P4 required learning a ton of concepts for what P4 thinks your workflow ought to be”

“Perforce does get the job done and it's reliable and stable.”

“P4 is also really well integrated into IDEs and UE Editor so that I don't need to think about it as much as I need”

“it has and continues to utterly fail at improving at a reasonable pace”

“perforce is the best out there for a variety of reasons. None of them are good.”

“Perforce is an relic of the 20th century that must die in a fiery inferno.”

“The GUI covers 99% of daily used operations and is easy to use.”

“It was sold to private equity about 10 years ago, and it feels like they've been coasting ever since.”

“In P4, you can add restrictions to certain directories for only those who have signed the required NDAs.”

“Perforce has decent integrations with the game engine editors my friends work with”

“Outside of something like Perforce, I've not used a VCS with a worse UI.”

“handle binary files better than Git when i tested it”

“Great for controlled environments, but not really built for open collaboration or community growth”

“its one weakness is its terrible security defaults”

“There's a reason why game studios use things like Plastic SCM and Perforce.”

“it does have some features that git still struggles with”

“their graphical tools for navigating a merge based history are excellent”

“Perforce allows you to lock a file so everybody else cannot make edits to it.”

“Perforce and Fuel are the two i like the most”

“other game development tools integrate Perforce better than Git”

“Perforce handles large files, and large folders of files, very well.”

“it's an overall better fit for (bigger) game projects”