Subversion in 2010 and Beyond
subversion.wandisco.com
Subversion in 2010 and Beyond
1–10 of 32 posts
Re: Subversion in 2010 and Beyond
#2I'd be interested to hear the opinions of HN'ers. Is there any reason these days to choose SubVersion over git?
Re: Subversion in 2010 and Beyond
#3I'd be interested to hear the opinions of HN'ers. Is there any reason these days to choose SubVersion over git?
" Is there any reason these days to choose SubVersion over git?"
Well sometimes your co workers are too .... old fashioned... to grok git. Work in a large enterprise sw company to see this at full effect.
Re: Subversion in 2010 and Beyond
#4Some interesting data from a survey: http://www.ddj.com/architect/222301141
Quote: "More than one-third of developers use Subversion for source code management; that's almost triple the share of the next most used SCM tool, Microsoft SourceSafe"
Re: Subversion in 2010 and Beyond
#5I'd be interested to hear the opinions of HN'ers. Is there any reason these days to choose SubVersion over git?
To the best of my knowledge, git is for smaller teams that need more of an ability to be dynamic (maybe web apps dev) whereas subversion is for larger teams that need centralization (network/server; maybe large systems - however Torvalds would disagree here since git was initially for kernel dev).
Re: Subversion in 2010 and Beyond
#6Some interesting data from a survey: http://www.ddj.com/architect/222301141 Quote: "More than one-third of developers use Subversion for source code management; that's almost triple the share of the next most used SCM tool, Microsoft SourceSafe"
That sourcesafe is the second most used SCM scares me.
Re: Subversion in 2010 and Beyond
#7I'd be interested to hear the opinions of HN'ers. Is there any reason these days to choose SubVersion over git?
" Is there any reason these days to choose SubVersion over git?" Well sometimes your co workers are too .... old fashioned... to grok git. Work in a large enterprise sw company to see this at full effect.
This. I think that the question that most large software companies are asking is "Is there any reason to move to git over subversion?" And in a large software company, that's a pretty big question. In fact, discussing it would likely take more time than actually moving to git.
Re: Subversion in 2010 and Beyond
#8I'd be interested to hear the opinions of HN'ers. Is there any reason these days to choose SubVersion over git?
To the best of my knowledge, git is for smaller teams that need more of an ability to be dynamic (maybe web apps dev) whereas subversion is for larger teams that need centralization (network/server; maybe large systems - however Torvalds would disagree here since git was initially for kernel dev).
Having Git be a distributed VCS doesn't mean it can't have a centralized server though. If you want you can use Git as something very similar to Subversion--you just lose out on a lot of the nicest parts of Git.
I think the biggest challenge with using Git in a large organization is training a large number of people to use it. You can do a fair amount of development on a Subversion project knowing just how to update and commit. The same does not hold true of Git.
Re: Subversion in 2010 and Beyond
#9Some interesting data from a survey: http://www.ddj.com/architect/222301141 Quote: "More than one-third of developers use Subversion for source code management; that's almost triple the share of the next most used SCM tool, Microsoft SourceSafe"
It is always fun seeing stats like this. Almost all of my friends have moved over to Git (one is on hg) so it is a fun reality check that Git is still small and has a long way to grow.
Re: Subversion in 2010 and Beyond
#10I'd be interested to hear the opinions of HN'ers. Is there any reason these days to choose SubVersion over git?
1) You don't know Git, but everyone in your group knows subversion.
2) The existing projects are already in subversion
3) The Subversion GUI tool which from the presentation it looks like a good portion use.