Shared objects are not only shared on disk, but their code segments are also shared in memory between executables that depends on the same libraries, lowering f

Shared objects are not only shared on disk, but their code segments are also shared in memory between executables that depends on the same libraries, lowering footprint and loading time. The reason dependency hell arises is because there is a lack of discipline in setting the soname correctly according to a semantic versioning (i.e. someone change the interface without changing the soversion) When soname is set correctly, there isn't really that much difference between /usr/lib and the GAC in Windows.