Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • What are some specific things you like about 'git' ? I especially interested if you could compare it to darcs, but comparing it to svn would be interesting, too.
    • I have only used both git and darcs for fairly simple use cases, and in my limited and unqualified opinion, they're very close to each other in terms of what they can do. git struck me as faster and as easier to install. It doesn't yet have the interactive commit (record) that darcs has, but this is apparently in the works.

      My third-hand knowledge tells me that the repository structure of git is incredibly simple, which is why there have been other implementation of it. Someone linked to a page called "Why Repository Formats Matter," but I don't have the link, and finding it over my cell modem would be a drag.

      I haven't yet done a lot of branching and merging, but from what I have watched and read, it is far, far easier to merge than in Subversion. It's trivial to branch in Subversion, but merging is still a pain. (Of course, this is better than in CVS, where merging is death itself.)

      The distributed nature of git is really keen, and I'm looking forward to being more involved with projects that use git, just to be forced to get a beter grip on using it.

      I'll be perfectly honest: I picked git because it was easy to install, provided a fairly simple migration path for my simple repo (without Taylor, thankfully), and my first few experiments went well. I spent a long time waffling between darcs and git, and git is just what I ended up deciding to use. I think this will end up being a good decision based on the architecture of the git repo and its porcelain/plumbing tools. I think those will lead it to become more successful than darcs, but that's just armchair prognostication.

      Jeez, though... git is fast.
      --
      rjbs
      • Thanks for the response.

        In terms of "installing darcs", I usually just drop a binary into /usr/local/bin/. It has a few minor dependencies, like "libcurl". However, it's been stable enough lately that a recent pre-packaged binary for a given platform is probably fine.

        I seem to recall there was a darcs-subproject to have it be able to be a client for a git repository, but I quit following that since I don't need that feature.