News for hackers. Stuff that matters.
Re:Why You Should Switch from Subversion to Git by axod on Wednesday September 16, 2009 @11:50AM (#826045)
How can you not be aware of pain? If I was wasting time on a laborious task, I think I'd know about it and think of a better way. Care to share an example from your experience?

During my average day, I probably spend a few minutes total messing with svn. For my usecase, it's already optimum. The only way I could reduce that time is to not put in any commit messages :/

Re:Why You Should Switch from Subversion to Git by timwiseman on Wednesday September 16, 2009 @12:10PM (#826093)
How can you not be aware of pain?

Anecdotally, this is fairly common. I have known people that did not realize they had fairly bad back pain until they went to the doctor for something else and had it treated.

Sometimes, it is only in absence of something that we really notice it, especially if it is truly chronic. I suspect most people have gone somewhere with a fairly loud background noise. At first they may notice it, but after being there for a while they may forget about it and may even forget it was ever there. But they will notice and realize how annoying it was if that noise ever stops.

Re:Why You Should Switch from Subversion to Git by axod on Wednesday September 16, 2009 @12:33PM (#826166)
I don't think the analogy holds here though.

I type 'svn commit' 'svn update', it works. quickly.

For me, it's like suggesting I change from using 'cd' to change directory, to using 'awesome-cd' to change directory :/

Re:Why You Should Switch from Subversion to Git by timwiseman on Wednesday September 16, 2009 @01:14PM (#826283)
I have never used SVN or Git (I use Hg at home and VSS at work), so I can't say there.

What I can say is that I didn't realize how painful Java was for me until I started learning Python. That may be a closer analogy, though still not perfect.

Re:Why You Should Switch from Subversion to Git by pmichaud on Wednesday September 16, 2009 @01:16PM (#826292)
Why would I switch from horses to these new-fangled automatic carriages? Horses get me where I need to go.
Re:Why You Should Switch from Subversion to Git by warp on Wednesday September 16, 2009 @02:43PM (#826516)
Here is an example from my experience:

Sometimes when I'm developing, and ready to commit something I notice I've made a few unrelated changes/bugfixes. I could just commit the whole thing at once, but that makes merging a hassle because I probably want to merge those bugfixes to trunk much sooner than any code which implements a new feature. So, I would need some way to commit only certain diff chunks from each file.

I understand from "http://www.gitcasts.com/posts/interactive-adding that git can do that. So far it hasn't been incentive enough to switch, but it's one example of the pain of subversion.

Re:Why You Should Switch from Subversion to Git by FooBarWidget on Wednesday September 16, 2009 @08:36PM (#827171)
Try 'git add -p', it's a lot easier than interactive mode.
Re:Why You Should Switch from Subversion to Git by FooBarWidget on Wednesday September 16, 2009 @08:32PM (#827160)
I don't know how, I just realized it after the fact. One good example is the use of branches. I began with CVS and switched to Subversion later. I always avoided branches because keeping track of merging points and resolving conflicts is a pain. I used to think that branches cause more problems than they solve.

Until I switched to git. Only then did I realize how much pain I was suffering by avoiding branches. Now I use branching all the time.

I guess it's because I had nothing to compare to. I didn't know that branches can be done well.

Re:Why You Should Switch from Subversion to Git by steveklabnik on Wednesday September 16, 2009 @01:42PM (#826365)
When your server's drive crashes, and you lose all of your history... you'll feel some pain. Backups help, but not as good as git does.

See what happened with _why? He nuked everything, but none of it really went away. With CVCS, the community would have lost everything.