News for hackers. Stuff that matters.
Re:You Cannot Correctly Represent Change Without Immutability by Dylan16807 on Wednesday July 04, 2012 @12:26PM (#4199944)
It does seem to mix a lot together. And the title is easily proved wrong. You can store data as a live object and a linked list of diffs to go further back in time. This is how the git pack file and many backup systems work.
Re:You Cannot Correctly Represent Change Without Immutability by Robin_Message on Wednesday July 04, 2012 @12:53PM (#4200051)
That is just an efficient way to store the original object and linked list of diffs to get to the current object (assuming accessing the current object is more popular). Note that if you store the original and the diffs, those things are all immutable.

Indeed, that is how git works in general – recording changes as immutable commits, and having one or more heads which point to the new immutable commit.

Re:You Cannot Correctly Represent Change Without Immutability by Dylan16807 on Wednesday July 04, 2012 @02:10PM (#4200299)
Right, you can flip it to make everything immutable, but then accessing the current object is O(t).
Re:You Cannot Correctly Represent Change Without Immutability by quorn3000 on Wednesday July 04, 2012 @04:10PM (#4200713)
And then you have SourceSafe
Re:You Cannot Correctly Represent Change Without Immutability by eru on Wednesday July 04, 2012 @04:39PM (#4200785)
I understood that git stores snapshots, and not diffs. At least conceptually.
Re:You Cannot Correctly Represent Change Without Immutability by Dylan16807 on Wednesday July 04, 2012 @10:03PM (#4201462)
Conceptually it's snapshots. At the lower level of pack files it's diffs.
Re:You Cannot Correctly Represent Change Without Immutability by DigitalJack on Wednesday July 04, 2012 @06:04PM (#4200957)
It does both.