4 ms·
Node's popular `pm2` itself is AGPL. I don't think they're too fussed about copyleft.
by arnon 7y ago
Node's popular `pm2` itself is AGPL. I don't think they're too fussed about copyleft.
- correct_horse 7y ago> I don't think they're too fussed about copyleft. Yeah, and I'm not either. I have never decided to vendor dependencies, and my only modifications to GPL code were to upstream (so I didn't have a legal obligation to distribute the modified code - the distributors of the code I modified do). I just think automated license compatibility checking could be a good move for the ecosystem. Also to be clear, I was talking about npm-like ecosystems. In my mind this includes npm, poetry and cargo (and probably more).
- oaiey 7y agoI hope on your comment you do not mix up LGPL and GPL.
- baybal2 7y agoNode has tons of AGPL packages which seem to be uses by quite a lot things. I myself saw a pm2 error message in Linkedin's error 500 output
- oaiey 7y agoA GPL or AGPL software should not exist on NPM for libraries. For tools yes, but GPL for libraries is for 99% of the users a non-starter. It just does not belong into a library ecosystem. To be clear: everyone has the free right to license their stuff how they like. I just think NPM as a ecosystem should be opinionated (and it is... Towards MIT. Just not completely).