Earlier quoted context omitted.
>if you are attempting to exploit other peoples code with out giving anything back to the people that created the code then GPL is a cancer That's bullshit - GPL requires you to open source your derived work as well - which plenty of people have a problem with commercially - it doesn't mean you don't want to contribute anything (quoting you) back. Even with the LGPL there are scenarios where sharing your code is not…
> In general GPL creates a lot of problems to which GPL supporters just plug their ears and mantra "if you were truly free you wouldn't have those problems". I'm not plugging my ears. I recognize it, and it's terribly unfortunate that one would ever be in such a situation, but the idea there is that the GPL would encourage the liberation of other code, and other platforms. Here's an example: http://clisp.cvs.sourcefo…
I work on a OpenStack project that does DNS. We have plugable drivers for the different software out there - PowerDNS, Bind9, nsd, etc.
One of the people deploying our software wanted (or needed? - there was some weird legal / support issue) to plugin into Nominum.
Now, to even look at the API ref, or use the Nominum python lib, you need to have a support contract, and agree to not release them. If we were GPL, that user would not be able to use our project, but because we were Apache they could write an internal driver, and still have the same API as other OpenStack users.