3 ms·
No, actually, Darcs is not, it only looks like it is. Again, unless it's recording key strokes and line changes you actually made in the editor, it's still just
by DannyBee 14y ago
No, actually, Darcs is not, it only looks like it is.
Again, unless it's recording key strokes and line changes you actually made in the editor, it's still just approximating what happened with a text diff algorithm that doesn't know what you actually did, and is figuring it out after the fact.
Besides not having the goal of figuring out what changed, they often are heuristic and give up (IE they stop trying to align the original files, and just say "removed here, added there").
- Silhouette 14y agoNo, actually, Darcs is not, it only looks like it is. I think that's a little unfair. Darcs does store what actually changed between the files, at least at the points they were committed, in a qualitatively different way to the flattening effect of cumulative commits in a system like say Git. Of course, you can defeat even that approach if your edits from one commit to the next are ambiguous, for example if you have two verbatim copies of something next to each other where you had only one before, and this will subsequently lead to ambiguity if you try to merge a change from someone else to the original copy since the merge has no way to determine whether the first or second duplicate (or both) should be modified. It sounds like you want something that is directly tied into your editor, so it is aware of changes between commits, or perhaps something that has semantic understanding so that instead of recording half a dozen text edits, it records "variable foo was renamed to bar". Tools that worked on that level would be fantastic to work with, but until you've swapped a text file representation of code for some sort of database-backed semantic model and your edits/refactorings can all be expressed in terms of that model, I don't see how any VCS could possibly achieve it.
- DannyBee 14y agoIt's really not qualitatively different, it's just faster for the operations it provides. It does, however, take great pains to try to display to the user the "right thing". It also does in fact, not lose information once given it. But that actually is not qualitatively different than you could make git or svn or anything else, it's just a more careful implementation. As for the rest, i don't want anything. I just don't pretend that textual displays of blame/diff/etc are actually showing me a correct history, instead of one possible history of textual changes. If it says bob wrote/changed some code, i don't assume that's really correct (unless of course, the changelog says "wrote code" :P), I ask bob. I will point out that historically, there were version control systems that were integrated like you describe, even for C++ (IBM Visualage C++). But people are happy with what things like git/svn/etc provide, and that's fine by me. Remember that I worked on a system whose sole goal was to provide a qualitatively better experience than CVS, so I don't have very high standards :P.