3 ms·
I'm a bit annoyed at how the discussion here has turned out. Did you actually read the post you're criticizing instead of just jumping at the first critical poi
by m_mueller 13y ago
I'm a bit annoyed at how the discussion here has turned out. Did you actually read the post you're criticizing instead of just jumping at the first critical points he makes about git because it happens to be your favorite tool? No argument you list here is in any way contradicting to what the post says.
To summarize again, the post says: Git is more powerful because it's distributed - but that comes at a price in terms of a more complex UI. If you know that you'll never need DVCS, you might be better off using SVN.
Everything you are listing here is examples of how git's UI is more complex, except you don't seem to recognize it anymore because git has become so engrained in what you do. Every so often it's worth it to take a step back, to look at our workflows and to figure out why we do what we do for every step. This SO reply was IMO a good attempt at explaining exactly this in terms of the Git vs. SVN discussion.
- chris_wot 13y agoI'm a bit annoyed at how your response to me has turned out. Did you actually read my response which you're criticizing instead of jumping at the first "critical points" I make about the comments made about git by the user? Or is it because git is not your favourite tool? No argument you list here is in any way contradicting what I said. Yes, I did indeed read the post. I wasn't jumping at "critical points", I was pointing out that he doesn't seem to have his head around a DVCS like git. As I've pointed out a few times, the UI is not really more complex. There is literally one more step - git push - to have your changes "pushed" to a remote repo.
- chris_wot 13y agoI'll not edit the above reply. But I'm sorry I wrote that the way I did. It was very snarky and unnecessary. Apologies for bringing down the tone of the thread. :(