5 ms·
This could actually give Mercurial a big edge over Git for development environments where large binary files are a core part of your workflow - like game develo
by kevingadd 15y ago
This could actually give Mercurial a big edge over Git for development environments where large binary files are a core part of your workflow - like game development. Products like Perforce are a big hit in games precisely because they are really good at handling this specific class of file.
It's a shame, because I hate using Mercurial, but this would give me a very strong reason to use it for my game projects instead of Git.
- js2 15y agoHave you looked at git-annex? http://git-annex.branchable.com/ http://git-annex.branchable.com/
- grandinj 15y agoWhat don't you like about Mercurial?
- durin42 15y agoWhat in particular do you hate about Mercurial? I'm curious as a contributor to hg if there's anything in particular that might be fixable (obviously there are some sacred cows, but many things can be fixed just by turning on an extension).
- kevingadd 15y agoThere are lots of little usability issues I hate, but it's not really fair to call those the reason, since git has similar usability issues. It really all comes down to patch queues: They're awful. They're so awful that they make me dread writing code and make me wish I was using Subversion or CVS. Any time I need to move changes that aren't ready for trunk yet from one machine to another I can expect to spend hours figuring out what went wrong with mq this time and probably lose some work. Exporting/importing patches, etc - none of it has ever worked right for me on the first try and I've never found documentation that explains a way to use mq without pain and suffering. In comparison, importing/exporting patches with git is a snap. The lack of a good equivalent to git's rebase -i is also unfortunate, but not really a showstopper. Hell, maybe mercurial has an equivalent by now.
- durin42 15y agoYou don't have to use mq ever. I don't really use it anymore. I still have it enabled for the 'strip' subcommand (so I can discard revisions if I really need to), but I don't even use that. Instead, it's all rebase and histedit, with a sprinkling of bookmarks so I can keep track of many lightweight branches at once. Importing and exporting patches with hg is easy: http://selenic.com/hg/help/export http://selenic.com/hg/help/export http://selenic.com/hg/help/import http://selenic.com/hg/help/import (those links are the same output as 'hg help $topic') As for rebase -i, you want http://mercurial.selenic.com/wiki/HisteditExtension http://mercurial.selenic.com/wiki/HisteditExtension.
- rdtsc 15y ago> want http://mercurial.selenic.com/wiki/HisteditExtension http://mercurial.selenic.com/wiki/HisteditExtension. That that is the another problem -- extensions. You go and read how to do something in mercurial. Go try it on your machine doesn't work. After a while realize you have to enable an extension. Why not just enable all the useful extensions.
- durin42 15y agoFor one: Because many, many features have sharp edges I don't want exposed to newbies. 'git reset --hard HEAD^' for example. Another: anything that's in hg proper has really strict backwards compatibility promises. Extensions let us screw around with a concept until the UI is _right_.
- rdtsc 15y agoMakes sense. Maybe it is already implemented, but I imagine it would be possible to let the user know that they are attempting to use an extension and said extension is disable and suggest how to enable it. Something like Ubuntu's missing command package works. If I type a command that is missing but is installable by a package in apt, there will be a suggestion printed "It looks like you are trying to use this command, it can be installed via apt-get ..."
- illumen 15y agoYeah, and web development. 4 gig repositories are fairly common on big web development projects with big graphics files taking up a lot of space.
- EGreg 15y agoWhy do you hate using mercurial? You like to type things like this: git fetch <project-to-union-merge> GIT_INDEX_FILE=.git/tmp-index git-read-tree FETCH_HEAD GIT_INDEX_FILE=.git/tmp-index git-checkout-cache -a -u git-update-cache --add -- (GIT_INDEX_FILE=.git/tmp-index git-ls-files) cp .git/FETCH_HEAD .git/MERGE_HEAD git commit instead of this: hg pull --force <project-to-union-merge> hg merge hg commit Mercurial "just works", and its commands are less arcane. To be fair, git is now much easier to use. But also to be fair, mercurial has become much more powerful. In mercurial, doing straightforward things is simple, and doing complicated things is more complex, which is the way it should be IMHO It even has rebase, although one might argue that is not a great differentiating feature for a REPOSITORY
- windsurfer 15y agoUnion-merging is insane and thus should take some insane understanding of what you're doing before you can do it. Anyone that's merging two unrelated repositories should understand what's going on under the hood anyways. What you're doing in git actually makes sense, since a normal pull is just fetch+checkout+merge+commit, you have to go into the plumbing and trick every step of the way to fetch, checkout, and merge using the wrong repositories. In the future, this could be made porcelain as it has been in hg, but do people really want to do this? It's much safer and saner to use submodules for 99% of use cases.
- EGreg 15y agoI still think people prefer git to mercurial these days (if we ignore github) for the same reason they prefer vim because real programmers use butterflies. http://xkcd.com/378/ http://xkcd.com/378/
- kevingadd 15y agoWhat does that even do? I've never had to do anything remotely that complicated with git. Try using patch queues for a while and tell me that Mercurial "just works" and isn't arcane. Nonsense.
- 15y ago