News for hackers. Stuff that matters.
Re:Version Control Before Git with CVS by oblio on Sunday July 08, 2018 @12:47PM (#17484718)
I still don’t like the Perforce model of workspaces or whatever they call it (clients?). That mapping between the server folders and your local ones. Extra complexity for no obvious benefit I could see.
Re:Version Control Before Git with CVS by vvanders on Sunday July 08, 2018 @02:27PM (#17485301)
For the right use case workspaces are awesome.

We used to do code + art in the same 1TB perforce repo back when I did gamedev. Art folder was ~600GB. Having a workspace to eliminate that as a developer was awesome.

Git still fails to even approach the usefulness that P4 brought to those types of shops. Between the auto-cache proxies, dealing with 1TB+ repos and workspaces there's a reason P4 still does pretty well.

Re:Version Control Before Git with CVS by oblio on Monday July 09, 2018 @04:12AM (#17488701)
I won't reply to all the comments saying mostly the same thing, but Git doesn't have this, true. SVN, another centralized system, does have it. Shallow checkouts plus folder checkouts and you can have any combo you want. Without adding another concept to take care of.

Much simpler conceptually, in my opinion.

Re:Version Control Before Git with CVS by a-dub on Sunday July 08, 2018 @03:54PM (#17485838)
It was great for large projects. I worked on a project that was similar to Android. Imagine 10 device trees (device drivers), two OS trees (Linux, vxWorks), and two application trees (the old stuff, the new stuff). You could define a mapping that got you just the trees you needed, which both sped up builds and VC operations (although p4's local indexing made most VC operations lightning fast).

Imagine a world where 'svn up' or 'cvs up' takes 20 minutes. Not only did the client mappings limit the scope of the operations, but local indexing brought the time for those operations down to 0-4 seconds.

Re:Version Control Before Git with CVS by solipsism on Sunday July 08, 2018 @01:49PM (#17485111)
The complexity is completely optional. Your client map can just map the entire depot to a single directory. And it has always been very easy to enforce this at the organizational level, with a small script in the server.
Re:Version Control Before Git with CVS by pjc50 on Sunday July 08, 2018 @02:28PM (#17485305)
It allows you to check out small bits of a really large repo.
Re:Version Control Before Git with CVS by st26 on Sunday July 08, 2018 @07:04PM (#17486787)
Rule of thumb, one man's useless version control feature is another man's saving grace. I've never needed to open multiple changelists simultaneously in one work area, but I'm sure someone loves that feature.
Re:Version Control Before Git with CVS by cousin_it on Sunday July 08, 2018 @04:06PM (#17485895)
Yeah, the mapping was a wart. Piper+CitC is much nicer, it's a file system that pretends you have the whole tree locally, while actually storing only the stuff you changed.