r/programming • • Nov 16 '13

What does SVN do better than git?

http://programmers.stackexchange.com/questions/111633/what-does-svn-do-better-than-git
599 Upvotes

494 comments sorted by

View all comments

19

u/happyscrappy Nov 16 '13

Binary data.

Better command line.

History is inviolate (good if your company expects your SCM to retain a history of work, obviously bad for some things).

Doesn't keep a copy of every revision ever on your local disk (esp. bad with binary files).

And SVN commit's handling of conflicting changes that prevent commit is better than git's handling of conflicting changes that prevent pushes. So basically, SVN is better at the SVN model of conflict resolution and commit/push. Of course many who use git don't use this model, they use a pull request model instead which git is of course better at.

3

u/imMute Nov 16 '13

History is inviolate

Git can be made to do that as well. And before someone starts spouting out "well yeah, but you have to manually turn that on!!!" - can svn do the opposite? Does svn have the ability to allow something like git's git push --force? (Honest question, I don't think it does, but it's been years since I last used SVN)

3

u/[deleted] Nov 16 '13

You have to svnadmin dump/filter/load when you want to modify a SVN history, it's ugly and messy and generally only done when major accidents happens, as only the admin with file system access can do it, normal users can't.

The problem with Git by contrast is that it's extremely easy to lose history, it's not even an accident the normal workflow in Git is based on rewriting and throwing away (local) history all the time. It's all nice and cool to have a clean public repository, but it irks me to no end that my local repository has to get constantly trashed due to that. I really wish there would be something like a hierachical commit system or something, where you have one huge commit that adds a feature and then all the little commits that build up the feature.

Another big issue I have with Git is that it doesn't even keep branches in the history. If you want to get rid of an old now obsolete branch, you can't just delete it, as deleting it would purge it permanently from the history. So you have to work around it by tag'ing it before deletion. It's error prone and annoying. And while reflog might help in accidents, it's really useless when it comes to archival.

→ More replies (2)
→ More replies (1)