Personally, I would say SVN reliance on remote server too much. Being able to create a repository and committing offline is one of the best features of Git.
Also, Git commands aren't really that confusing. It might just take a while if you are switching from SVN though because of the difference in concepts. If you are starting with Git (like I did), I don't think it's confusing at all.
I actually started with CVS, slowly adapted SVN and I found myself in the VCS wars only a little later. I had to work with Git at my previous workplace, I killed my code more often than not thanks to Git's weird branching...
Yeah. Branching concepts are bit different. In Git, a branch simply means a pointer to a commit while in SVN it means a copy (shallow) of a trunk (with ancestry information).
I had to use SVN about a year ago on a project and I was not a fan of how commits were lost while merging into another branch.
(I recently convinced the project to be moved to Git, though. :P)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thank you for your comment.
What overhead are we talking about? If we are talking space, Git takes up much less.
Ref: git.wiki.kernel.org/index.php/GitS...
Personally, I would say SVN reliance on remote server too much. Being able to create a repository and committing offline is one of the best features of Git.
Also, Git commands aren't really that confusing. It might just take a while if you are switching from SVN though because of the difference in concepts. If you are starting with Git (like I did), I don't think it's confusing at all.
I actually started with CVS, slowly adapted SVN and I found myself in the VCS wars only a little later. I had to work with Git at my previous workplace, I killed my code more often than not thanks to Git's weird branching...
To each their own, I guess.
Yeah. Branching concepts are bit different. In Git, a branch simply means a pointer to a commit while in SVN it means a copy (shallow) of a trunk (with ancestry information).
I had to use SVN about a year ago on a project and I was not a fan of how commits were lost while merging into another branch.
(I recently convinced the project to be moved to Git, though. :P)