Re:Don't be a git, use subversion
by wting on Wednesday May 01, 2013 @11:57AM
(#5638727)
Umm... fuck no.
There is no reason that you can't use git as a master repository system--that's how most people treat GitHub anyway.
OTOH if you want to do anything besides the basic commit or update with Subversion, it's ridiculously difficult. Subversion is a SCM tool where people actually prefer to merge manually rather than deal with its conflict handler.
Re:Don't be a git, use subversion
by MetaCosm on Wednesday May 01, 2013 @01:03PM
(#5639189)
Because git is significantly faster, better at merging, allows cheap private branching and private changes (don't have to do everything in public just to have version control), allows staging of changes, allows offline work, allows "out of band" collaboration between developers, is up to 30x smaller repos (mozilla), more redundant (everyone has full history)... (more)
Re:Don't be a git, use subversion
by gte910h on Wednesday May 01, 2013 @11:48AM
(#5638656)
If you must keep with subversion, explicitly authorize the use of git-svn for developers who are using git.
Git use causes smaller incremental commits, which can be squashed into bigger ones for re-merging, but makes for better, more ambitious changes, and easier rollbacks to working code. You get 85% of the benefit by allowing those who can handle it to use git as a subversion client.
Re:Don't be a git, use subversion
by dguaraglia on Thursday May 02, 2013 @04:43PM
(#5647106)
I think what the author is trying to say is that by saving a command for 'every action' that you take on git, you can offset the hours and hours of conflicts and manual work you get every time you try to merge a branch into trunk on SVN. Or maybe not.
Re:Don't be a git, use subversion
by marcuskaz on Wednesday May 01, 2013 @01:32PM
(#5639400)
There are complexities with DVCS that people gloss over focusing only on the positive. My view is that the complexity is rarely worth it for most company settings.
Re:Don't be a git, use subversion
by caoimhin on Wednesday May 01, 2013 @06:35PM
(#5641279)
There are more and more devs who have only worked with git. For them, they will find svn complex. They'll be used to using branches and svn will get in their way.
Git is complex for you. The mistake you're making is in not realising that's not universally true.
Re:Don't be a git, use subversion
by marcuskaz on Thursday May 02, 2013 @08:52AM
(#5644129)
A very good point, and something I've considered. You might just be right and I'm just getting old and crotchety :)
I still see git requiring more commands for simple tasks and the model of what is happening has more moving parts (more complex). This gives git the ability to do a lot more, but my thought is for the majority you don't need the more.
Re:Don't be a git, use subversion
by marcuskaz on Thursday May 02, 2013 @09:04AM
(#5644181)
I don't think I created any controversy. The real controversy is whether you should use rebase or not.
My thought was just simplify and subversion might be the right tool for many jobs.
Everyone thinks I'm a fool.
As far as stats, if you really are curious. I received about 1,600 views on the article. Oddly no referrer data from HN, around 300 from Twitter, 150 from Google Reader and 100 from hckrnews.com.
There is no reason that you can't use git as a master repository system--that's how most people treat GitHub anyway.
OTOH if you want to do anything besides the basic commit or update with Subversion, it's ridiculously difficult. Subversion is a SCM tool where people actually prefer to merge manually rather than deal with its conflict handler.
It will save you a command on every commit, no need to commit and then push.
Git use causes smaller incremental commits, which can be squashed into bigger ones for re-merging, but makes for better, more ambitious changes, and easier rollbacks to working code. You get 85% of the benefit by allowing those who can handle it to use git as a subversion client.
This article explains the complexity well: http://steveko.wordpress.com/2012/02/24/10-things-i-hate-abo...
Git is complex for you. The mistake you're making is in not realising that's not universally true.
I still see git requiring more commands for simple tasks and the model of what is happening has more moving parts (more complex). This gives git the ability to do a lot more, but my thought is for the majority you don't need the more.
My thought was just simplify and subversion might be the right tool for many jobs.
Everyone thinks I'm a fool.
As far as stats, if you really are curious. I received about 1,600 views on the article. Oddly no referrer data from HN, around 300 from Twitter, 150 from Google Reader and 100 from hckrnews.com.