3 ms·
I'm not sure how many people struggling to learn git (the 'git novices' of the article) are competent with any comparable tool. Maybe "why git is hard" isn't th
by qwery 3y ago
I'm not sure how many people struggling to learn git (the 'git novices' of the article) are competent with any comparable tool. Maybe "why git is hard" isn't the right question?
Speaking from personal experience, if you already learned Mercurial, you might find it annoying that commands with the same name do different things, or worse: almost the same thing, but it's practically the same[0] system. Coming from a centralised system to a decentralised one is a bigger jump but understanding the 'distributed' part of "distributed version control system" seemed to me (speaking from personal experience) pretty straightforward, compared to the V, C, & S.
It's just that a lot of the points made here seem only loosely git-related? Not that that makes them wrong or invalid, by any means -- they do all apply to git. Fully agree that teaching people `git fetch` as a separate thing to `git pull` is probably wise.
[0] the same: git doesn't believe in curtains, mercurial just painted and doesn't need curtains
- JohnFen 3y ago> I'm not sure how many people struggling to learn git (the 'git novices' of the article) are competent with any comparable tool. I am extremely competent with a couple of other version control systems, but that doesn't really help me in terms of understanding git. I agree that many of the attempts to explain it that I've read (including a number of the comments here) are really explaining things that all version control systems have in common. For me, those aren't the parts that I struggle with. It's how those things map onto actually using git that I find difficult.