Hacker News Reader

> even SVN is something I'd like to have a night of good sleep before accepting.

Why's that? SVN may not be fashionable, but it's centralised, has ACLs and a hook system.

Because it will be a huge mess once you hit your first merge conflict or want to use proper branches. SVN is usable for source code management, but not really for efficient collaboration.

edit: And if the SVN server goes down / messed up by someone, you're essentially forced to sit around and staring into the sky. With git, all you may have to do is fiddle a bit with merging if someone did a git push --force. And if the server is down, you still are able to work on your own.

As someone who uses git and svn a lot, I'll say that git has more end user features. You can do so much more with git than svn. If you have to work on svn, you'll have to give up those features.

It might be a warning sign as well. An organisation on svn might be an organisation that doesn't upgrade and is resistant to change.

Reply on news.ycombinator.com