DEV Community

Discussion on: Why Git instead of SVN

Collapse
 
elmuerte profile image
Michiel Hendriks

SVN puts hidden subfolder into every subfolder in your project

This hasn't been the case for quite a long time. You now have a single .svn in the root, just like with git.

I also seem to remember SVN always copied all files instead of changes for some reason, so it took a lot more space.

The .svn contains a "pristine" copy of the file in your workspace. This is an exact copy of the file when checked out. It is just one version of the file.

Git on the other hand stores all versions, from the cloned repo. Unlike SVN, GIT compresses the files. For a repo with a few versions it will be smaller, but once the repo grows it will start to consume more space than SVN does.

Again I don't know if SVN has changed since, but with Git you could commit on your local all day long, then push changes when you want, and it wouldn't mess things up between you and co-workers, while I believe SVN you had to keep it synced all the time?

SVN is still centralized, committing is always to the server. You won't mess things up between you and your co-workers unless people are working on the same files.

Collapse
 
perttisoomann profile image
Pert Soomann

Like I said it was quite long time ago, would be surprised if SVN didn't improve. Good to know.