3 ms·
Is Git really that hard to use? I know it took me awhile to learn how to find the right documentation for things, but that's significantly easier these days tha
by moron4hire 12y ago
Is Git really that hard to use? I know it took me awhile to learn how to find the right documentation for things, but that's significantly easier these days thanks to StackOverflow and the like. All told, I don't find Git significantly more difficult than the other tasks I have to do for my job. Usually, the troubles I have had with Git were because I tried to do something the wrong way.
And if you don't like the documentation, well, there's more than one way to contribute to an open source project.
And you could make an argument about Git specifically having bad UX in certain ways, but that isn't an argument against DVCS in general.
There are problems and bugs with every VCS out there, but I've never encountered one with Git that left me completely useless for a day, or with a completely corrupted, unrecoverable repository. I've heard of such things happening in Git, but it hasn't happened to me in 5 years of using it. I've had that happen to me, personally, once every 8 to 12 months using SVN. The we thought SVN was a godsend back then was because it wasn't the 3 to 4 months that was SourceSafe or the monthly rate that was CVS.
Okay, I'm being bit hyperbolic there, but not by much.
And you can model centralized VCS in DVCS--evidenced by the fact that many peopled do do that with Github and it's ilk--meaning that systems that can only do centralized VCS are defective. Git can do everything SVN can do, but SVN can't do everything Git can do.
If your central SVN repository goes down, you're pretty much SOL until it comes back, and you might even be SOL if and when it does come back. If GitHub goes down, I'm mildly inconvenienced when I have to add a new remote to my repository when I need to, say, share code with a colleague, or perform a deployment.
The argument about contributions is... it's not about Git or DVCS at all. It's about GitHub and/or bad project maintainers. And he even admits that, but then acts like he's delivered a blow against the general concept of DVCS.
The argument about blobs is an argument against Git, but not DVCS.
I can't speak to Hg or Baz. I've heard they are easier to work with than Git. But I just can't imagine giving up the things Git gives me to go back to SVN. If someone on one of my projects suggested such a thing, it would seriously call into question for me that person's expertise.
- acveilleux 12y agoWell, I picked up CVS in about 30 minutes. Getting the nuance of DVCS right is much harder, at least when used in a distributed way with a team. I learned Mercurial first and Git still took me longer to grok.
- ufo 12y agoIts a bit annoying that I still have to frequently go back to stackoverflow whenever I need to do a git operation I haven't done in a while. Git doesn't have strong abstractions and the commands are organized in a very adhoc manner so its hard to predict how something will work without having to go check some documentation.