4 ms·
I would go with mercurial. It just works well with both Windows and Linux (I don't have a MAC). And like alfred said, hoping is not a good option for you. I wo
by atiw 17y ago
I would go with mercurial.
It just works well with both Windows and Linux (I don't have a MAC).
And like alfred said, hoping is not a good option for you.
I would always go with any tool, that's proven that obscure.
Playing around with it, and testing it is fine if you are a <4 people team.
Anything more than 4, and I think it's time to google "XYZ number of users" and it will show you stuff.
If you still need more information to be sure, I think I trust these two, esp recommend the google code link.
http://code.google.com/p/support/wiki/DVCSAnalysis http://code.google.com/p/support/wiki/DVCSAnalysis
http://rg03.wordpress.com/2009/04/07/mercurial-vs-git/ http://rg03.wordpress.com/2009/04/07/mercurial-vs-git/
This one is a little balanced. more like a good info on internals of both. A little too long, and I didn't like the fact that the guy says both are great, in summary.
I knew that already...pick a side if u write a VS article...or else what's the point.....
- JeremyBanks 17y agoMAC?
- atiw 17y agooops, meant to say OSX
- rg3 17y agoI'm the author of the second one. I don't pick a side because I use both for different personal projects and haven't made my mind up yet. It's an honest conclusion and the article is oriented to giving an introduction to someone who's trying to make a choice. That's the point.
- atiw 17y agoRg3, I went back and had another look. I take my words back (if that's ever possible :) ). I assumed the purpose of writing that article as saying I pick this, if pushed to the corner (as is the case in our startups). I will have to say it's a fairly good introduction. I like the amount of details provided.