Live data from Hacker News

Subversion in 2010 and Beyond

subversion.wandisco.com

11–20 of 32 posts

Re: Subversion in 2010 and Beyond

#11

I'd be interested to hear the opinions of HN'ers. Is there any reason these days to choose SubVersion over git?

We've had this debate before, but something along the lines of:

* No GUI for Git on Windows

* Everything knows how to work with Subversion already (tools, testing, continuous integration, idiots)

* Companies like centrally controlled and backed up solutions

* Why change when what you have works for you

Re: Subversion in 2010 and Beyond

#13
post #11

I'd be interested to hear the opinions of HN'ers. Is there any reason these days to choose SubVersion over git?

We've had this debate before, but something along the lines of: * No GUI for Git on Windows * Everything knows how to work with Subversion already (tools, testing, continuous integration, idiots) * Companies like centrally controlled and backed up solutions * Why change when what you have works for you

What do you mean no GUI for Git on Windows? There's the excellent TortoiseGit http://code.google.com/p/tortoisegit/, along with numerous other tools that you can find on the Git wiki.

Re: Subversion in 2010 and Beyond

#14
post #11

I'd be interested to hear the opinions of HN'ers. Is there any reason these days to choose SubVersion over git?

We've had this debate before, but something along the lines of: * No GUI for Git on Windows * Everything knows how to work with Subversion already (tools, testing, continuous integration, idiots) * Companies like centrally controlled and backed up solutions * Why change when what you have works for you

The same guys who make SmartSVN, have SmartGit now...

Re: Subversion in 2010 and Beyond

#17

I'd be interested to hear the opinions of HN'ers. Is there any reason these days to choose SubVersion over git?

Git is significantly more complicated to learn, basically because having an additional level of repository and no default upstream repository makes for more moving parts. Git also has more flavors of branch (tracking or non) and repository (bare or not), and more ways to edit changes (cherrypicking, rebasing).

So basically, more moving parts means it takes more time to figure it out. For you or me, that's an inconvenience and then happiness about all the cool features and capabilities. For a corporation trying to keep their training budget low, that's a non-starter.

Re: Subversion in 2010 and Beyond

#20

I'd be interested to hear the opinions of HN'ers. Is there any reason these days to choose SubVersion over git?

Subversion has features Git doesn't and can't support.

Do you mean "Git has features Subversion doesn't and can't support"? :)
Post reply on HN