Yes, I thought about something like that. Being able to map it to the filesystem and back to the Unison database. But then, what is the point of this content a

Yes, I thought about something like that. Being able to map it to the filesystem and back to the Unison database. But then, what is the point of this content addressed code again? What do we gain from it that we don't already have now? With current file based version control you already have an append only repository, code is never deleted from the .git directory, it's just not always mapped to a file in the source code directory (until you check out an old revision, that is). Edit: I guess Unison still has the unique feature that dependencies are referred to by identity and not name.