> You can think of it as an incremental build step but the crucial key that Unison's content addressing gives you is that canonical representation only needs to

> You can think of it as an incremental build step but the crucial key that Unison's content addressing gives you is that canonical representation only needs to be generated once, ever. That's not very different from using ccache. Claiming that there are no builds is simply not true. > So for example if someone publishes a library, no new build step would ever be required for consumers of that library. Does that require trusting compiled blobs from 3rd parties? That could make it trivial to inject backdoors.