3 ms·

You're not, and I think this is where a lot of flamewars between Git and Mercurial users and between DVCS and centralized VCS users start, so I while I don't wa

You're not, and I think this is where a lot of flamewars between Git and Mercurial users and between DVCS and centralized VCS users start, so I while I don't want to feed the fire, I will only cautiously recommend peeking at Joel Spolsky's Hg Init tutorial, and see if Mercurial is a bit more natural for you, since a lot of people seem to think it's simpler (I have no opinion, mostly because I haven't used Mercurial much). At the end of the day, for me it boils down to a comment by Xiong Chiamiov, made on one of Mike Taylor's rant-y blogposts about Git, which was much discussed on HN a while ago, "I use it because the benefits outweigh all of the things that you mentioned." Yeah, it's complicated. But a lot of people think it's worth it. edited to add links to the Reinvigorated Programmer posts, which I recommend reading because there's a ton of good commentary and suggestions for newcomers, even if the discussion got a bit heated: http://reprog.wordpress.com/2010/05/10/git-is-a-harrier-jump-jet-and-not-in-a-good-way/ http://reprog.wordpress.com/2010/05/10/git-is-a-harrier-jump... http://reprog.wordpress.com/2010/05/12/still-hatin-on-git-now-with-added-actual-reasons/ http://reprog.wordpress.com/2010/05/12/still-hatin-on-git-no...

skrebbel 15y ago
Thanks for the advice. However, I felt exactly the same with Hg. In fact, the main reason I have for currently using git and not hg is github. I'm convinced that indeed it's worth spending more time to grok [git/hg/bzr] and really get the power out of it, but I just can't shake the feeling that somehow, it should be possible to make something with the same benefits that works much easier. I was hoping that maybe Kiln is exactly that, but from their promo-page all I can see is a rant about how cool DVCSs are, and not much about how Kiln makes Hg easier.
- spacemanaki 15y ago
  I use Git for the same reason, although there's also Bitbucket and others for Hg. I don't want to act as an apologist for Git, because I think the user-interface could use some work (although I gather it was much worse earlier). I think at the end of the "Git from the bottom up" tutorial the author wishes the interface were better, but believes that Git will be the base upon which awesome things will be built. I don't know if anyone has tried to create a kind of porcelain-above-the-porcelain of Git, but that might be interesting, although from my experience with 3rd party Git GUI tools (Tortoise, EGit), many of which abstract details away, it can also be infuriating if done poorly. I don't think the current DVCS are the best thing ever possible, but I do think Git one of the best things we have now.
- sjs 15y ago
  Here's the key to git: embrace the fact that you're going to learn a new tool. Learn how to use it and play around with it. Once you're comfortable doing the basic things you would do day to day like create a repo, commit, push, pull, branch, merge, etc. then dig in deeper. Now you start reading about how git works under the hood to demystify the things you already know. Articles like "Git for Computer Scientists" are great at this stage. Once you know how git's incredibly simple model works you are well poised to learn more advanced things. Rebasing can be hard for some people to understand and it's even harder if you don't know what commits and branches actually are. After that you need little instruction and should be able to help yourself. It's totally worth it and it's not as hard as you think! edit: Plus once you know how it works you get to skip big parts of articles like this and just skim around to pick up what you don't already know. It's pretty light reading actually.
- stonemetal 15y ago
  Kiln is basically a bitbucket competitor. It doesn't really change Hg(they do sponsor development ), what it does do is provide a nice web front end and provide the rest of the tools a project would need(through fog bugz) like wiki, bug tracking, scheduling etc.

skrebbel 15y ago

Thanks for the advice. However, I felt exactly the same with Hg. In fact, the main reason I have for currently using git and not hg is github. I'm convinced that indeed it's worth spending more time to grok [git/hg/bzr] and really get the power out of it, but I just can't shake the feeling that somehow, it should be possible to make something with the same benefits that works much easier. I was hoping that maybe Kiln is exactly that, but from their promo-page all I can see is a rant about how cool DVCSs are, and not much about how Kiln makes Hg easier.

spacemanaki 15y ago
I use Git for the same reason, although there's also Bitbucket and others for Hg. I don't want to act as an apologist for Git, because I think the user-interface could use some work (although I gather it was much worse earlier). I think at the end of the "Git from the bottom up" tutorial the author wishes the interface were better, but believes that Git will be the base upon which awesome things will be built. I don't know if anyone has tried to create a kind of porcelain-above-the-porcelain of Git, but that might be interesting, although from my experience with 3rd party Git GUI tools (Tortoise, EGit), many of which abstract details away, it can also be infuriating if done poorly. I don't think the current DVCS are the best thing ever possible, but I do think Git one of the best things we have now.
sjs 15y ago
Here's the key to git: embrace the fact that you're going to learn a new tool. Learn how to use it and play around with it. Once you're comfortable doing the basic things you would do day to day like create a repo, commit, push, pull, branch, merge, etc. then dig in deeper. Now you start reading about how git works under the hood to demystify the things you already know. Articles like "Git for Computer Scientists" are great at this stage. Once you know how git's incredibly simple model works you are well poised to learn more advanced things. Rebasing can be hard for some people to understand and it's even harder if you don't know what commits and branches actually are. After that you need little instruction and should be able to help yourself. It's totally worth it and it's not as hard as you think! edit: Plus once you know how it works you get to skip big parts of articles like this and just skim around to pick up what you don't already know. It's pretty light reading actually.
stonemetal 15y ago
Kiln is basically a bitbucket competitor. It doesn't really change Hg(they do sponsor development ), what it does do is provide a nice web front end and provide the rest of the tools a project would need(through fog bugz) like wiki, bug tracking, scheduling etc.