News for hackers. Stuff that matters.
Re:Anu: A sound, distributed version control systema by wtracy on Thursday November 05, 2020 @04:41PM (#25002316)
Soaking as someone who is completely unfamiliar with Pijul, the explanation on this page is pretty lackluster.

"It is based on changes rather than snapshots"

Well, every VCS I'm familiar with is based on changes/deltas. I assume that these terms have specific meanings here that I'm not familiar with, but it manages to sound like the author has never heard of git or Mercurial.

Re:Anu: A sound, distributed version control systema by zanecodes on Thursday November 05, 2020 @04:56PM (#25002463)
Git actually does not work with deltas; each commit contains the hash of a tree object [0], which contains the hashes of the files within it [1]. This tree is effectively a snapshot, since it contains every file hash in the working directory at a certain point in time. Since Git uses the file hash instead of just the file path, it doesn't have to download the files whose hashes haven't changed since the last commit, which is what makes it behave somewhat as if it is operating on a delta.

[0] https://git-scm.com/book/en/v2/Git-Internals-Git-Objects#_gi... [1] https://git-scm.com/book/en/v2/Git-Internals-Git-Objects#_tr...

Re:Anu: A sound, distributed version control systema by tomjakubowski on Thursday November 05, 2020 @04:51PM (#25002415)
git fundamentally tracks and stores snapshots, not changes. I believe mentioning this is meant to emphasize a difference between Anu (or Pijul) and git.
Re:Anu: A sound, distributed version control systema by ben509 on Thursday November 05, 2020 @05:42PM (#25002901)
This is correct. The common misunderstanding is due to the fact that gits pack files are delta compressed, but that's a implementation detail.