I think that content addressability works really well for code, at the bottom layer. But in order to be practical, you typically need: Naming and resolvers, in

I think that content addressability works really well for code, at the bottom layer. But in order to be practical, you typically need: Naming and resolvers, in order to be human friendly. This isn't easy to get right, but we have a lot of prior art in dependency management systems. Persistence layers with GC, like cache and db. You're gonna want to fetch and prefetch in ways that are quite advanced. You don't want to be be blocked in a critical section by network fetching the leftpad function.