3 ms·

If you just update an encryption library and ship only that… then who’s tested all the applications against the new version?

• salawat 5y ago
  Not the library author's problem. That's the consumer's problem. I'm not saying it's great, but it's how it works.
  • chrisseaton 5y ago
    > That's the consumer's problem. Well this is the explanation for why people are static linking! They don’t want to run someone else’s entirely untested code and bear all responsibility for any problems.
    • salawat 5y ago
      For the record? I'm totally fine with that. As I'm basically one of the static linking group, or "use dynamic libraries in a way non-distinguishable from static linking". If I'm relying on it, it's getting tested and I'm not going to dork with it without good reason once it is.