Conversation

You misunderstood me - while technically possible, the ability to incorporate GPL software into proprietary software products is severely restricted. And yes, having to use out-of-process extensions to avoid the GPL propagation to proprietary code is limiting.
1
GPL restricts usage and is a close cousin of those non-commercial licenses. Permissive licenses do exist. Complying with licenses is itself a choice. GPL violation is the software equivalent of pirating a movie. Many people choose not to respect software licenses anyway.
2
2
You're playing on the words here - yes, the GPL is applicable at distribution time, but having to distribute essential components of your software separately comes with several restrictions on how you can use it, the first one being that you can't link it statically.
1
Hahaha, thanks for the condescending explanation! You see, the primary consumers of *source code* are... developers! Maybe it wasn't the case originally, but in today's world, the "users" you are talking about use prebuilt software, they almost never build it from source.
2
But if you must insist on that specific definition of "users" that aren't developers - I reject it entirely. Why? Because an open source license should protect the rights of the developers first. You may disagree, but I value my own rights as a developer more than as a user
1
Show replies