Hacker News new | ask | show | jobs
by teddyh 1003 days ago
> The problem with the GPL is that its "infectious" nature does not play nicely with how the B2B world works, where you might link against your client's in-house proprietary libraries, which even though they're never planning to distribute them, they very much don't want their own IP to become GPLed as a result.

Standard GPL FUD. Firstly, linking against proprietary libraries is fine as long as you don’t distribute the result to any third party. Secondly, no IP can “become GPLed” unless anybody chooses to make it so.
1 comments
red_admiral 1003 days ago
Some of the companies I've worked with, and their lawyers especially, have explicitly said that for them anything GPL in the application layer was a no-no (Linux as OS was fine though). This is on code that will never be distributed outside internal systems.
link
teddyh 1003 days ago
Company lawyers being weird and wrong about GPL, film at 11. The GPL paranoia strikes deep.
link
cies 1003 days ago
AGPL though is avoided by the plague by corp lawyers, and for good reasons. Hence I like it for some projects.
link
teddyh 1003 days ago
No, not for very good reasons.
link
type0 1002 days ago
> anything GPL in the application layer was a no-no (Linux as OS was fine though).

well, just proves how hypocritical it is

link