I suppose it can be helpful if seeing a folder full of revisions would otherwise drive you crazy. I mean, I fully admit I also sometimes just dump a mess from my desk into a drawer just so I don’t have to look at it constantly.
Also, if you have a consistent habit of writing accurate and descriptive commit comments, you may not need to rely on being able to compare line-by-line diffs to see what’s changed between versions.
I think the moral of the story is that git is a somewhat suboptimal tool for this purpose and it whether it’s helpful at all depends far more on your habits and discipline than on the functionality it provides.
If something appeared that handled opaque data better, it would take some thinking before creating the repository. Currently, there’s no reason to think at all.
Outside of being able to comment on each revision when making a commit, I guess I don’t see what benefit this provides that regular, automated backups (such as Time Machine) don’t.
I suppose it can be helpful if seeing a folder full of revisions would otherwise drive you crazy. I mean, I fully admit I also sometimes just dump a mess from my desk into a drawer just so I don’t have to look at it constantly.
Also, if you have a consistent habit of writing accurate and descriptive commit comments, you may not need to rely on being able to compare line-by-line diffs to see what’s changed between versions.
I think the moral of the story is that git is a somewhat suboptimal tool for this purpose and it whether it’s helpful at all depends far more on your habits and discipline than on the functionality it provides.
AKA the best we have around.
If something appeared that handled opaque data better, it would take some thinking before creating the repository. Currently, there’s no reason to think at all.
Outside of being able to comment on each revision when making a commit, I guess I don’t see what benefit this provides that regular, automated backups (such as Time Machine) don’t.