5 ms·
To me github is the killer feature of git. I think svn is easier and more appropiate for a corporate environment.
by huherto 14y ago
To me github is the killer feature of git.
I think svn is easier and more appropiate for a corporate environment.
- jlgreco 14y agoReally? Git seems like the killer feature of Github to me... Why do you think that git is inappropriate for a corporate environment? I've been using it in one for a few years now and see nothing wrong with that.
- delano 14y agosvn is fine for very small, highly co-ordinated teams which is rare in a corporate environment. It's decidedly not fine for complex merging, development outside of the private network, or maintaining multiple versions of the same codebase (customer installs) among other things.
- Peaker 14y agoEven then, doing without "add -p", "rebase -i", "commit --amend", inplace branches, and various other git features is going to cost you.
- FuzzyDunlop 14y agoI think the killer feature of git -- which applies to any other DVCS -- is that you're not dependent on github if you're well prepared. There's absolutely nothing stopping you adding redundant remotes so you always have somewhere to push/pull changes and deploy from. git remote add <remote_name> url
- hp50g 14y agoYep and that's like managing dns with host files...
- rubyrescue 14y agothe achilles heel of svn is branches cost 100% of the branched repository. even an svn repo with one user can be prohibitively large. even in a corporate lan environment just pulling down an svn repository can take far too long
- huherto 14y agoWhy do you say branches are expensive? http://stackoverflow.com/questions/2041/how-do-i-create-a-branch-in-svn http://stackoverflow.com/questions/2041/how-do-i-create-a-br...
- zevyoura 14y agoYou have to maintain a full copy of the file tree locally per branch, it's a pain that gets worse as your project size grows. With git, switching between branches is near instantaneous.
- hp50g 14y agoIt is in svn as well (200mb wc switch = 4 seconds).
- zevyoura 14y agoI worked in an environment with a significantly larger repository, and svn switches were a constant source of frustration.
- banachtarski 14y agosorry but that is a very long time. Branching is something I do dozens, if not hundreds, of times a day (creating, checking out, deleting, etc). svn doesn't fit the sane modern workflow and everything it does can be done by git in a less painful manner. I think the only use case I can think of for svn is a very binary heavy repo that needs global locking.
- rubyrescue 14y ago