|
If you listen to tech media you'd think that everyone uses Git, and a handful of us old coots still use SVN. I use both, but given the choice I choose SVN every time.
|
|
|
|
|
Yvan Rodrigues wrote: I use both, but given the choice I choose SVN every time.
Same here. Unfortunatelly, I seldom have a choice...
|
|
|
|
|
You put your finger on Git's success: GitHub.
GitHub is often chosen because it's easy. Setting up a new repo is trivial, and that's why both open-source and corporate users use it.
The closest thing to GitHub for SVN is SourceForge, I guess; maybe Google Code or CodePlex. None of these are as easy to use as GitHub, and SVN has never had a site to champion them.
In my case I run my own SVN server, but if I didn't I might end up using GitHub (or ::Workspaces)
|
|
|
|
|
Did you know that Github does SVN too, now? You can have SVN access to the Git repo, it's not like you have to choose Git or SVN!
Er, I can't think of a funny signature right now.
How about a good fart to break the silence?
|
|
|
|
|
Last time I checked, SVN access was read-only.
|
|
|
|
|
Well, Git can be confusing and not easy to handle on multiple platforms. But you will try Mercurial only once and fall in love. The TortoiseHg makes your projects so much more transparent and the Gui is the same on all platforms. Even the command line interface is so much easier to learn. Try it out (and choose for yourself, this is my opinion, no need for a war).
|
|
|
|
|
That's why I haven't tried Mercurial. I don't want to fall in love with another tool that isn't widely adopted.
|
|
|
|
|
> I don't want to fall in love with another tool that isn't widely adopted.
I don't think that is a big problem, as it is adopted widely enough (see http://mercurial.selenic.com/wiki/ProjectsUsingMercurial[^]) to stay supported.
And then there are the SVN and Git etc. plugins, so you can first try it out and convert your repositories later ... but stop, I am getting carried away now. If you have a look at it, you may cause even more people to have a look at it and fall in love, so it will be automatically be more widely adopted.
|
|
|
|
|
I used to use SVN but switched to Git with a healthy dose of marketing scepticism but have to say I much, much prefer Git.
Git itself I find overly complex and inconsistent in its argument structure, but in this enlightened, latte drinking world of ours there are plenty of excellent GUIs and Explorer add-ins that make the use painless.
Two specific things I prefer in Git:
1. I can do a series of local commits and then push them all in one hit to the origin (and rebase if I'm feeling clever to ensure a neat history). This saves us from the "never commit broken or not-working code" rule we have internally. You can go a day or two between clean builds in dire times and being able to save a restore point can be a life saver.
2. No centralised repository. We;;, we do have a repo we use as the central repository, but that's merely a nomination. If that server is unavailable we each have a full copy of the repo and can sync up between ourselves perfectly fine. No more server crash terrors.
cheers
Chris Maunder
|
|
|
|
|
I've used TFS and SVN in the past, but now that I'm used to Git I am not going back, ever!
It's just better.
|
|
|
|
|
I hated Git when I started using it. But after about a month of using it, I got used to it. Now I can't imagine going back. After using Git, I got to experience TFS for the first time and found it much slower to use.
Hogan
|
|
|
|
|
HomerTheGreat wrote: It's just better
Meh. I spend way too much time helping people with Git. Never had that problem with any other source control system and I've used quite a few.
|
|
|
|
|
In connection with CP Workspaces. At least for personal projects.
The console is a black place
|
|
|
|
|
I use Git for my personal projects, but my employers uses SVN.
djj55: Nice but may have a permission problem
Pete O'Hanlon: He has my permission to run it.
|
|
|
|
|
|
AND. ME.
Sorry, I'm assuming that capitalisation was the way to go...
Er, I can't think of a funny signature right now.
How about a good fart to break the silence?
|
|
|
|
|
Because the company I contract to right now uses SVN, Jenkins and JIRA and while it just about works, it's a pain in the arse.
|
|
|
|
|
Having to move onto TFS -I can't say I am enjoying the experience. I have managed without source control for 25 years and can't recall a time when I would have needed it. I have always backed up my entire source base into zip files from time to time - but in all that time have only ever recovered code from it twice
|
|
|
|
|
I have used source control heavily in the past and it is useful for teams but sometimes it is just me on a project and I am also happy with my backups, which I rarely need.
So many details! (heavy sigh) So much confusion...
|
|
|
|
|
In my case, I often revert a few files when doing changes that does not works as intented... Also, I often look at the history to find when something was changed or changes that might cause a bug.
For professionnal working, I find it hard to works a few hours without comparing changes or reverting something.
By the way, I am using PureCM at works.
Philippe Mori
|
|
|
|
|
I think because I have never really used it I haven't come to rely on it or to work in such a way which needs source control.
I can appreciate it for teams but I rarely work within a team
|
|
|
|
|
You put your code in a CListCtrl, each version in a different row and each branch in a new column, and then you eat enough bacon amounts to have your veins enough saturated not to think much about it... and you are set.
|
|
|
|
|
It is a legacy thing, I had source control before everyone else, they worship at the alter of Microsoft, there is only me left working on the stuff in SVN.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
|
TFS is good, but the will of Microsoft to control developers life can kill me (I'm referring to changes between versions, that force you to go and upgrade your TFS every year)...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
Not a must option but still it's quite common
--
The trouble with people, is that they want to hear only what they want to hear.
|
|
|
|