4 ms·

> For the exact same effort, you can view changes to past revisions, revert any single file to a previous version, see exactly what you changed and when. Tarba

> For the exact same effort, you can view changes to past revisions, revert any single file to a previous version, see exactly what you changed and when. Tarballs let you do that as well. > You said your are a solo developer Right. Those people are working on their own code base (total disaster, much of it due to branching and following the VCS "methodology". I feel like slapping their lead whenever he mentions tagging or branching. That stuff ain't free! You only have one brain! /rant)

wvenable 16y ago
> Tarballs let you do that as well. No, they don't. I can right-click on any file and view all the changes as a diff, I can see exactly what I changed and when, and revert that file back to any previous version. You can't do that with a tarball -- at least not without significantly more effort. It's just better all around. > Those people are working on their own code base (total disaster, much of it due to branching and following the VCS "methodology". You're not required to use any particular methodology. I've seen people screw up with every technology in existence -- that's hardly a reason to head back into the woods and live like a cave man. There are very few things in the field of computing science that are universally agreed on. There are dozens of development methodologies, thousands of different programming languages, IDEs, etc. The closest thing we have in this business to consensus is the use of version control (even if the exact tool to use is still under debate). You're simply mistaken to assume not using version control is superior in any way to using it. There's nothing wrong with your own methods of development and backup but that isn't version control and it isn't incompatible with it either.