Re:Copyleft and community licenses are not without merit, bu...
by cyphar on Saturday December 22, 2018 @01:26AM
(#18739294)
If you can replace an LGPL component with a changed version then you don't need to license any additional code under the LGPL. Shared libraries are just one mechanism for doing this.
I think the LGPL becomes something just like the GPL for scripting languages because there is no "linking" for many languages.
For example an npm package for nodejs can't be made into a "library" - all the source is "compiled" together at runtime.