3 ms·
Good luck. I mean that. Git isn't perfect, but I've been using version control since Apple Projector (in the late 1980s), and Git has done the best for me. I'v
by ChrisMarshallNY 6y ago
Good luck. I mean that.
Git isn't perfect, but I've been using version control since Apple Projector (in the late 1980s), and Git has done the best for me. I've been using it for many years.
I don't miss Projector one tiny bit.
VSS (Visual SourceSafe) was a dog. It was direct file-based, and server connections would get very busy. It was the old-fashioned kind, with the need to check out files.
But it had one very cool feature: You could create "aliases" of repo components; essentially creating a virtual repo that pointed into several other repos, taking just a couple of files from each.
I could see how that would be a technical nightmare to implement, but I like it a lot more than "the whole kit & kaboodle" approach that Git takes.
I also used Perforce for many years. It was a robust and dependable system, but had that need to check out files to work on them, and that drove me nuts.
I like Git, because it is "team-friendly," and has a really light touch. It encourages many small checkins, which is how I think I should usually work.
I wish it handled big files better, but that's not really a big deal to me. I think this might be why Perforce is still preferred for game development (their asset libraries get big).
Oh, also Submodules suck like a supermassive, galaxy-core black hole.
- skissane 6y ago> I've been using version control since Apple Projector (in the late 1980s) Never heard of Apple Projector before. I've always been interested in the history of version control systems, so I would like to learn more about it. But when I search for the term, almost all I find is stuff about using projectors with Macs/iPhones/iPads/etc. Can anyone point to any information sources on it?
- ChrisMarshallNY 6y agoYah...you're right. I'll see if I can scare it up. It was integrated into MPW. UPDATE: It gets a brief mention in the "Legacy" section of the MPW Wikipedia page: https://en.wikipedia.org/wiki/Macintosh_Programmer%27s_Workshop#Legacy https://en.wikipedia.org/wiki/Macintosh_Programmer%27s_Works... It's obscure for a reason. It was the best back then, but was still a nasty bear.
- karlding 6y agoIt's mentioned in the book Programmer's Guide to MPW: Exploring the Macintosh Programmer's Workshop by Mark Andrews [0]. [0] https://vintageapple.org/macprogramming/pdf/Programmers_Guide_to_MPW_1990.pdf https://vintageapple.org/macprogramming/pdf/Programmers_Guid...
- ChrisMarshallNY 6y agoOh...Gods. Reading that, brings back the horror...
- fsflyer 6y agoAfter Metrowerks' CodeWarrior became popular, Projector was still used. There was a CodeWarrior plugin for it: https://www.mactech.com/1997/12/20/md1-cwprojector-1-0-released/ https://www.mactech.com/1997/12/20/md1-cwprojector-1-0-relea... In later versions of MPW, Projector was split off as a separate executable, SourceServer. Searching for MPW SourceServer finds a number of hits.
- FpUser 6y agoVSS - I was using it as well but I bought some product (forgot the name) that was a server facing the Internet and handling all the communication to VSS on behalf of multiple clients. Perforce - I used it too but after their upgrade killed the repo I got rid of it. I understand that it could've been my fault but still ... After that it was Git
- boris 6y ago> Oh, also Submodules suck like a supermassive, galaxy-core black hole. They suck like a chainsaw would sucks for cutting twigs. But they are very effective (together with symlinks) when you need to stitch an amalgamation of multiple repositories (which themselves could be stitched from multiple repositories). That's not to say you don't loose a finger or two now and again.
- ChrisMarshallNY 6y agoTrue, dat. I used them for this project: https://riftvalleysoftware.com/work/open-source-projects/#baobab https://riftvalleysoftware.com/work/open-source-projects/#ba... It's a long chain of submodules, and making tweaks to the lowest layer means a lot of pulls. I was able to semi-automate it with a couple of batch files. I didn't use Composer, because I figured that this was a project that would remain fairly static, and submodules are "native" (I am always a bit leery about depending on third-party package managers). Which has been the case, except that I'm writing an app that uses it as a backend, so I've had to make a few changes lately.
- user-the-name 6y agoNo, no, no. They just suck. It's not that the concept is bad - it is in fact very good, for the exact reason you suggest. They are just abysmally badly implemented. They barely work at all and frequently get your repo into nonsensical states for NO REASON other than that the tooling is utterly worthless. Mercurial has subrepos that offer conceptually the exact same functionality, but is actually implemented in a way that works WITH you rather than against you, and that will not constantly break. Git submodules are just a completely unfinished feature that is nearly unusable.