News for hackers. Stuff that matters.
Re:'Hot migrating' from SVN to mercurial, and why we choosed... by zdw on Sunday May 15, 2011 @12:19PM (#2550180)
TL;DR: They have windows developers, git isn't optimized for use on windows, whereas HG runs well wherever Python is available.
Re:'Hot migrating' from SVN to mercurial, and why we choosed... by pnathan on Sunday May 15, 2011 @01:37PM (#2550337)
This accords with my experience as well. I've found HG to be more intuitive to use: less immediately exposed commands, branches were 'obvious', and the help has been absolutely superb.

Further, it Just Works on OSX/Windows/Linux (providing the Python is compiled right...).

The big downside to hg IMO is its repository size as opposed to git. I keep a fair number of PDF documents in one repo, and a hg-git conversion drops the size by quite a lot.

Re:'Hot migrating' from SVN to mercurial, and why we choosed... by bostonvaulter2 on Sunday May 15, 2011 @04:31PM (#2550723)
What do you use to do the hg-git conversion?
Re:'Hot migrating' from SVN to mercurial, and why we choosed... by eridius on Sunday May 15, 2011 @05:12PM (#2550794)
I can't speak for pnathan, but I would assume he uses hg-fast-export.
Re:'Hot migrating' from SVN to mercurial, and why we choosed... by andrewcooke on Sunday May 15, 2011 @05:36PM (#2550833)
...and he also appreciates the ease of use.
Re:'Hot migrating' from SVN to mercurial, and why we choosed... by kevingadd on Sunday May 15, 2011 @12:57PM (#2550262)
How strange. In my experience TortoiseGit is far superior to TortoiseHG, and as a result as a windows developer I always choose git instead of Mercurial.
Re:'Hot migrating' from SVN to mercurial, and why we choosed... by zdw on Sunday May 15, 2011 @01:08PM (#2550281)
Good to know.

I wish there was an up to date comparison of current code out there - most of the "git on windows has problems" anecdotes I'm aware of are from at least a year ago.

Re:'Hot migrating' from SVN to mercurial, and why we choosed... by ghurlman on Sunday May 15, 2011 @01:09PM (#2550285)
Can you extrapolate? I've never liked Tortoise*, preferring to stick to the command line - how is T-Git better?
Re:'Hot migrating' from SVN to mercurial, and why we choosed... by stonemetal on Sunday May 15, 2011 @02:34PM (#2550452)
TortoiseHG's gui needs a designer. I have just about come to the conclusion it was made by someone who doesn't like HG as a joke. It doesn't use HG's terminology, it is fairly unintuitive.
Re:'Hot migrating' from SVN to mercurial, and why we choosed... by kevingadd on Sunday May 15, 2011 @01:19PM (#2550306)
TortoiseGit's UI is much better designed than TortoiseHG's - operations you want to perform tend to be exposed in more obvious places, with clearer names and simpler UIs. In many cases it offers commands that encapsulate a set of underlying operations; for example, TortoiseGit offers subversion-style Commit and Revert dialog boxes that behave like the equivalent dialog boxes in TortoiseSvn, even though Git has no directly analogous commands. This is really good if you want to get work done without being a Git expert.

In particular, Rebase in TortoiseGit has an excellent user interface that takes Git's command line rebasing process and turns it into a user-friendly graphical equivalent. I've yet to find any equivalently pleasant user interfaces in TortoiseHG; pretty much all of TortoiseHG's user interfaces are tangled messes of dropdown menus and checkboxes that try to reproduce every mercurial configuration switch.

TortoiseGit is also faster and more stable than TortoiseHG. I'm not sure if this is because TortoiseHG is largely written in Python+QT, or just because TortoiseGit is more mature - I use TortoiseHG a lot at work when interacting with mercurial repositories, and it crashes frequently, but I've never had TortoiseGit crash or freeze on me.

There are also a lot of UX problems with TortoiseHG that seem to originate in the design of Mercurial, though, so this may come down to my personal taste.

Re:'Hot migrating' from SVN to mercurial, and why we choosed... by alexandrul on Monday May 16, 2011 @07:48AM (#2552248)
Given that both tools have their ups and downs, my reasons for picking TortoiseHg for Windows development are listed on SO: http://stackoverflow.com/questions/2550091/best-support-now-...
Re:'Hot migrating' from SVN to mercurial, and why we choosed... by pnathan on Sunday May 15, 2011 @01:32PM (#2550325)
I tried to use TortoiseGit. I found it a practically unusable GUI compared to TortoiseHG.