Ironically, it says that the problem with git is you have to internalise it's model to use it effectively. But then describes JJ in terms of how it relates to what git does.
Talks about how it uses revisions not commits or something, but never really explains why it's good, just more that it's different to git.
So I think this is probably a very good article for someone who actually knows git, but isn't very good for the users he says would most benefit from it!
Comments
Ironically, it says that the problem with git is you have to internalise it's model to use it effectively. But then describes JJ in terms of how it relates to what git does.
Talks about how it uses revisions not commits or something, but never really explains why it's good, just more that it's different to git.
So I think this is probably a very good article for someone who actually knows git, but isn't very good for the users he says would most benefit from it!