3 ms·
I found the #1 reason to be incredibly ironic: > The information model is complicated – and you need to know all of it. As a point of reference, consider Subve
by dasil003 14y ago
I found the #1 reason to be incredibly ironic:
> The information model is complicated – and you need to know all of it. As a point of reference, consider Subversion: you have files, a working directory, a repository, versions, branches, and tags. That’s pretty much everything you need to know.
SVN's model is both simpler than stated here, but also much more complex to reason about. First of all, svn doesn't have branches or tags, it just has directories with cheap copy—tags and branches are just directories. The repository itself is also watered down pretty severely because the actual project directory is just nested in there somewhere with no formal locus. This idea of "everything is a directory" sounds simple, but in practice it's a architectural dead-end. The most obvious implication is that merging in svn will always be fraught with peril because a branch isn't a first-class citizen.
I used svn (and cvs before it) for much longer than git, and yet I never felt I had any clue what svn was doing under the hood, and the experiences I had over time instilled a fear of attempting to stray off the well-worn path of the most basic commands.
Although the learning curve was steep, and the CLI quite confusing, the git information model is actually much easier to grok because the primitives make more sense. After 6 months using git, I had a firmer grasp of the internals than I did after 10 years of cvs and svn. The idiosyncrasies of the UI don't really bother me because they are just superficial flaws that are easily memorized or looked up. The fact that I have the confidence to slice and dice commits to any history I can envision, with or without a network connection and remote repo, and do so with the reasonable confidence that I will never lose anything (reflog) make git the best VCS I can imagine.
- agumonkey 14y agoWith previous VCS I couldn't understand the limitations, with git I don't see limits.
- koglerjs 14y ago>SVN's model is both simpler than stated here, but also much more complex to reason about. Well, sure, but if I understand his intent it's to demonstrate that Git's not hugely superior in clarity to freaking SVN. I don't think he's defending SVN, though I'd only be completely sure of that if he mentioned hg at some point.
- jeltz 14y agoI have exactly the same experience. After 3 years working with svn I still hard problems reasoning about the data model and what for example a merge would do, while after just 2 months I understood git way better than I ever had done svn. Most of his list could easily be changed to be about svn instead. svn has a bad data model, svn has incomplete and poorly written man pages, in svn you need to run many commands to do simple things, svn has illogical command line parameters, ...
- perlgeek 14y agoI fully agree. SVN traditionally had some things that simply didn't work, often related to file renames. I remember trying to rename a file after 'svn add' but before 'svn commit', and it simply didn't work. Maybe that's fixed now, don't know. Or merging stuff when a file was renamed in one branch and changed in the other. During my several years of SVN usage I have regularly driven SVN checkouts against a wall, where I didn't manage to recover them into a usable state, not any combinations of revert, update or other commands. This has never happened to me with git.