On 1/28/2011 9:59 AM, Ted Byers wrote:
This may be adequate IF you're working alone and if you have all the time in the world, but it will become an unmaintainable nightmare when the number of programmers contributing to the project increases significantly and as time pressures grow. Imagine the chaos that would result from this if you had a dozen programmers doing this independantly to the same codebase.
You proceed from a false assumption. You might have 1000 commits in your local copy. When you're done, and ready to publish, you "push" it as one. No different than SVN.
commercial app that has half a million lines of code, or more, it is just too easy to break things (there are practical and commercial reasons for rational modularization as results in object oriented programming, as well as proper management/design of compilation units, &c.).
Again, no one sees your changes until your ready. It's there to help the individual. How often have you been in the middle of a large change to quite a few files, then said "oh, this sucks", and revert it. Then, a half hour later, you decide "Oh, wait, 100 of those lines (out of the 1000 you just threw away) might be useful". With SVN, you're hosed. With git, you're not.