in reply to Git vs Hg or GitHub vs Bitbucket for Perl projects

I was a git skeptic for very long, because I couldn't understand what the heck it is doing, or how I could do stuff with it.

Then rakudo switched to git, and I was forced to learn it to some extent. Now I'm sold to it, because it does all the offline working that I need, local branching, diffs and blame annotations in no time (that SVN would only give me with internet access and a minute of waiting), rebase etc.

I do see that it's rather confusing at first, and not very easy to learn.

I have not experimented with Mercurial or any other distributed version control system (except a bit playing with darcs and svk, both which didn't really appeal to me at that time) so I can't really comment on them, but I'm pretty sure that distributed version control systems are the way to go - which one exactly is really up to personal preference.

  • Comment on Re: Git vs Hg or GitHub vs Bitbucket for Perl projects

Replies are listed 'Best First'.
Re^2: Git vs Hg or GitHub vs Bitbucket for Perl projects
by Your Mother (Archbishop) on Apr 26, 2009 at 20:33 UTC

    ++. I've had--am having; not quite to cruising speed yet--the same experience. Not easy to jump into. Really not. "WTF are they talking about, Git sucks," not. But the more I get it, the more I really like it. Powerful and quick once you get over some of the conceptual differences from SVN/CVS. It's also been around long enough at this point that most "How do I..." Google queries turn up an answer from someone who had the same hurdle and got over it. I don't know Hg but I do know what little of Perforce I was once forced to use made me :(

      I don't know Hg but I do know what little of Perforce I was once forced to use made me :(
      Yeah, I must admit that Perforce is not that friendly. I did a lot of work related to it like writing some automatic branching stuff around p4 commands for example. But I think it'll be hard to do anything complicated with the help of `p4 help` or Googling around. Luckily we had the perforce book in the office. Does not have a 100% coverage but good enough :)