Hacker News new | ask | show | jobs
by wongarsu 3018 days ago

    anything with *GPL as its license
AGPL is obviously even stricter than the GPL, but I don't see the problem with LGPL in libraries? Worst case you end up making some improvements to the library that are applicable outside your application and have to publish the source for your changes to the library, but that seems only fair. In the vast majority of cases you don't modify library code, leaving you with no obligation.

You might run the risk of somebody copy-pasting code from a LGPL library into your production system, but I don't think that risk is greater than the risk of them copy-pasting from the first google result without checking the license.