3 ms·
> But after looking at other source control options, ... > Anyone ever had to do a diff of a Microsoft Visio document by hand? Anyone had to manually type in
by lelanthran 3y ago
> But after looking at other source control options,
...
> Anyone ever had to do a diff of a Microsoft Visio document by hand? Anyone had to manually type in the name of a document and its revision by hand into a web form? Anyone ever spent an afternoon working on a document, only to realize that someone else already made the changes you made but forgot to update the filaname which caused their changes not to be visible to you? Programmers are spoiled with the best tools in version control. People in other domains are doing this, without even knowing that they are doing this. They are making commits, merging, rebasing, etc.. without even having a word to describe it.
I don't see what that last paragraph has to do with git being any good. You're looking at the difficulty of collaboration without revision control, and saying "this shows how good this particular revision control system is".
If you think git is good because of that last paragraph, then it's no better than CVS.
- robertlagrant 3y agoThat isn't the point there. It's that we should be thankfuly for text-based tools in general, compared to most other professions' experience of digital collaboration.
- masklinn 3y agoThat has nothing to do with git then, and it very much fails to justify the assertion that > Any tool that deals with collaborative working on document will present the same issues that Git does. Maybe worse.
- lucideer 3y agoThat isn't the point I gleaned from reading it. The gp seemed to be making a specific point about Git, not about text based tools in general.