News for hackers. Stuff that matters.
Re:Mercurial over Git by lincolnq on Friday April 16, 2010 @03:22PM (#1271626)
Your use of the words "intuitive" and "revert" in this context betray that your models are driven by how you expect centralized version control to work.

While Git and Mercurial are nearly isomorphic in implementation, their UIs differ significantly because they're written with different models of DVCS in mind.

Basically, I would argue you haven't fully grokked Git. To the extent that I have understood Git's model, I have found it extremely insightful; if you want this insight, you should spend a little more time trying to understand it before giving up on it.

Re:Mercurial over Git by alexgartrell on Friday April 16, 2010 @04:28PM (#1271832)
As a long-time TA for the class leading up to 15-410 (almost as long as he's been a student at CMU) I can firmly attest to the fact that we have done absolutely nothing to make him aware of centralized version control (or distributed version control...) :)

So basically, he's got the freshest possible eyes to make this judgement, and if your counterclaim is that he hasn't truly grokked it yet, then that suggests that it may be counterintuitive.

Additional fairness: the project in question is a 6-week round-the-clock code fest. Writing a kernel from scratch takes forever. (Is this project just a waste of time? Having moved on to poking at the Linux kernel and stuff, I'd say almost certainly, but that's a topic for another conversation.)

Most Sincerely, Alex "Found out the hard way that reset != revert" Gartrell

Re:Mercurial over Git by jshen on Friday April 16, 2010 @07:05PM (#1272211)
" if your counterclaim is that he hasn't truly grokked it yet, then that suggests that it may be counterintuitive."

You should say, "it may be counterintuitive to him". Intuition is based on past experiences and our internal metaphors. We have no reason to believe that his "intuition" is the same as most of the population that would use git.

Re:Mercurial over Git by theli0nheart on Friday April 16, 2010 @04:40PM (#1271865)
> if your counterclaim is that he hasn't truly grokked it yet, then that suggests that it may be counterintuitive.

Or proper usage wasn't explained to him correctly.

Re:Mercurial over Git by wmcc on Friday April 16, 2010 @04:48PM (#1271894)
Since we learn from the online docs, doesn't your statement imply that Gits online documentation isn't very good?
Re:Mercurial over Git by pyre on Friday April 16, 2010 @05:18PM (#1271964)
> Since we learn from the online docs

That's an assumption.

Re:Mercurial over Git by mcn on Friday April 16, 2010 @05:46PM (#1272029)
wmcc stated he was in the same OS class as the blog poster.
Re:Mercurial over Git by blasdel on Friday April 16, 2010 @08:30PM (#1272331)
git is the first revision control system I've used where "revert" actually does what I "intuitively" expect it to: begin a new commit that reverts a commit in the history.

The rest of the clown-car VCSes use "revert" to go back in time to that commit in the history.

Re:Mercurial over Git by tghw on Friday April 16, 2010 @08:37PM (#1272342)
Clearly, you don't know your clown-cars.

Mercurial uses hg backout to start a new commit that backs out a previous commit, hg rollback to undo the previous transaction (without a separate commit), and hg revert does undoes the uncommitted changes in your working directory, very similar to MS Word's (now defunct) and Photoshop's (still active) File > Revert command.

To me, revert means "revert all my changes to the last saved version", which is exactly what Hg does.

Re:Mercurial over Git by blasdel on Saturday April 17, 2010 @03:42AM (#1272768)
I had another sentence in my post that I edited out that was a caveat to Mercurial: at least it's possible to get the 'git revert' behavior with hg without implementing it yourself from a patch-series dump.

To me, revert means "stage a new commit that reverts this commit in the history as if it never existed".

When I first used svn, I really expected 'revert' to mean "revert this commit". I also 'intuitively' expected it to have something like git's index, and ended up just working around that by just laboriously creating my own set of patches to feed it in another checkout. Not everyone's mental models line up — we are both free to consider one another as a moron (see also: politics, religion).