3 ms·
I don't see this as a decrease in freedom over the default situation, though. If code is copyrighted, third parties can't use your code in their software, unles
by _delirium 16y ago
I don't see this as a decrease in freedom over the default situation, though. If code is copyrighted, third parties can't use your code in their software, unless they reach a licensing agreement with you.
I see GPLing my software as making a limited quid-pro-quo exception: you can use my code for free, without individually negotiating a license, but only if you do the same with your software. If that situation doesn't apply, then I'm happy to license the software in the normal manner, as one proprietary software vendor doing business with another one.
My view is something like: If someone is writing a piece of proprietary software, they should understand what proprietary software licensing means, and be prepared to pay for a commercial license if they want to use someone else's code, just as they'd expect anyone else to pay to use their code.
- madhouse 16y agoWell put, thanks for expressing the other half of my thoughts :)