2 ms·

One main reason is licensing. Lots of good, basic libraries are lgpl. Like Qt etc... Also you'd want the basic libraries like glibc, ssl to be provided as shar

One main reason is licensing. Lots of good, basic libraries are lgpl. Like Qt etc... Also you'd want the basic libraries like glibc, ssl to be provided as shared libraries by the distros for various reasons - including security. That being said i do appreciate how newer languages like rust, go default to static linking.

kelnos 3y ago
> One main reason is licensing. Lots of good, basic libraries are lgpl. While this might be a little more annoying, you can absolutely statically link a proprietary application with an LGPL library. You do need to provide object files for the proprietary bits so someone could relink it with a different/modified version of the LGPL library, though. Which, yes, is annoying to the point that if I were distributing a proprietary application, I probably would use dynamic linking with the LGPL bits.