> If your code says "I depend on that hash", then the runtime needs to locate where the binary code that corresponds to that hash is located. And that's a depen

> If your code says "I depend on that hash", then the runtime needs to locate where the binary code that corresponds to that hash is located. And that's a dependency problem to resolve. It's not a dependency conflict though. > If someone fixes a bug in a dependency, your program may not be able to locate the hash anymore. You have to "re-build" your hashes everytime a dependency changes. Again, that's not a conflict. A conflict goes like this: Dependency A has a breaking change, but Dependency B transitively depends Dependency A as well, so you cannot update your own code until Dependency B also updates. Even if A and B are updated, you are prevented from adding any dependency that hasn't updated yet. You can't mix and match to use the old code in one place when you need it. This wouldn't be such a problem if programmers didn't break interfaces for dumb reasons all the time, but they do, so lots of people just run older versions of the software.