David Bremner<p><span class="h-card" translate="no"><a href="https://mastodon.social/@dabeaz" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dabeaz</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@shriramk" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>shriramk</span></a></span> <span class="h-card" translate="no"><a href="https://fediscience.org/@GeorgWeissenbacher" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>GeorgWeissenbacher</span></a></span> </p><p>I care about (shared) libraries in two contexts. The first is as a contributor to <a href="https://mathstodon.xyz/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Debian</span></a>, where shared libraries are really much better for security support (and other kinds of bug fixes). Things like Rust and Haskell require substantial effort and machinery to rebuild all dependencies of a changed libraries. That's fine on a developer machine, but not so great with millions of installed machines that you cannot OTA update a la google/apple. The second is as a maintainer of a free software project (<a href="https://mathstodon.xyz/tags/notmuch" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>notmuch</span></a>) where libraries (shared or otherwise) provide a practical way to share core functionality between several languages (at least Rust, Golang, Python, and Ruby) where I don't control any of the other language ecosystem.</p>