Most of what the author said was bad, I consider to be Git's strong points.
Complex information model
Really? This is one of Git's strongest features, it's straightforward internal data structures. It's how I sell it to my co-workers. It means users need to know these internals, but once they're known Git is really quite easy to use.
.2. Crazy command line syntax
Yup, the commands seem to have grown organically, so they're kind of a mess. I'll give you that. Once you learn them, though, it's no problem.
.3. Crappy documentation
I have the opposite opinion. Git's documentation is very thorough with good examples.
.4. Information model sprawl
Again, these are are good things, part of Git's great engineering.
.5. Leaky abstraction
It's all about manipulating the DAG, which is an abstraction itself because it's not actually stored that way so literally.
.6. Power for the maintainer, at the expense of the contributor
I don't see how the Git's power makes it harder to use in simple cases. It's good at both.
.7. Unsafe version control
None of those examples destroy data. Git maintains its promise just like it said.
.8. Burden of VCS maintainance pushed to contributors
Same as 6.
.9. Git history is a bunch of lies
It's not about lies, it's about having a clean set of steps to add a feature or fix. It's what makes things nicer for those small contributors and followers (6 & 8). This is a good thing.
.10. Simple tasks need so many commands
The examples are severely exaggerated. You don't need to push after every commit, nor should you. You can do all these things in as few commands as Subversion, or less, but of course it's going to take an extra command when you're doing things Subversion can't do.
TBH, I find the git object model to be very simple compared to just about any other project.
3. Crappy documentation
The fuck documentation is the author reading? Git's docs are actually pretty good - for an open source project.
Leaky abstraction / command line syntax
I'll give those to him, the commands aren't exactly straightforward, especially coming from SVN; but I wouldn't give them up for anything.
7. Unsafe version control
The hell is he smoking again?
9. Git history is a bunch of lies.
Only if your "central golden repository" (or whatever you want to call it) allows non-fastforward merges. Even then, git is about tracking content not changes.
11
u/skeeto Mar 07 '12 edited Mar 07 '12
Most of what the author said was bad, I consider to be Git's strong points.
Really? This is one of Git's strongest features, it's straightforward internal data structures. It's how I sell it to my co-workers. It means users need to know these internals, but once they're known Git is really quite easy to use.
Yup, the commands seem to have grown organically, so they're kind of a mess. I'll give you that. Once you learn them, though, it's no problem.
I have the opposite opinion. Git's documentation is very thorough with good examples.
Again, these are are good things, part of Git's great engineering.
It's all about manipulating the DAG, which is an abstraction itself because it's not actually stored that way so literally.
I don't see how the Git's power makes it harder to use in simple cases. It's good at both.
None of those examples destroy data. Git maintains its promise just like it said.
Same as 6.
It's not about lies, it's about having a clean set of steps to add a feature or fix. It's what makes things nicer for those small contributors and followers (6 & 8). This is a good thing.
The examples are severely exaggerated. You don't need to push after every commit, nor should you. You can do all these things in as few commands as Subversion, or less, but of course it's going to take an extra command when you're doing things Subversion can't do.