> As do the BSD and especially(?) the Apache Software License.
Suppose someone forked BSD kernel, modified it heavily over years and made a closed source product of out of it (you don't actually need to suppose it anyway). Users get zero out of four freedoms they would have gotten with GPL.
As a user, you now can't freely run the kernel on multiple computers as you like, you are not allowed to investigate what the binary blob actually does on your hardware, you're not allowed to give a copy to your friend, and you're not allowed to make patches and redistribute.
So while this worked very well for some company and allowed them to launch a series of products in series quickly (which translated into billions in revenues), it screwed all of the four basic freedoms for all (paying) users.
Now tell me, how exactly is BSD license going to protect my rights as a user here?
As for the original developers of BSD, I'm guessing they might have been happier if that company contributed (some of) their changes back. Or maybe a few bucks from the billions of dollars they made.
BSD license basically gave the company to screw everyone else, both end users and original developers. Only a free software license such as GPL protects them both.
> make the code more resistant to forks, esp. less free
GPL doesn't have any restriction on forks. At all. Re-licensing and forking are orthogonal concepts.
> opens an option for the original author of code to do dual-licensing
That doesn't have anything to do with GPL itself.
> provides an opportunity for the authors to prevent certain uses of the code
It guarantees that four freedoms mentioned in the above link are protected.
Suppose someone forked BSD kernel, modified it heavily over years and made a closed source product of out of it (you don't actually need to suppose it anyway). Users get zero out of four freedoms they would have gotten with GPL.
https://www.gnu.org/philosophy/free-sw.html
As a user, you now can't freely run the kernel on multiple computers as you like, you are not allowed to investigate what the binary blob actually does on your hardware, you're not allowed to give a copy to your friend, and you're not allowed to make patches and redistribute. So while this worked very well for some company and allowed them to launch a series of products in series quickly (which translated into billions in revenues), it screwed all of the four basic freedoms for all (paying) users.
Now tell me, how exactly is BSD license going to protect my rights as a user here?
As for the original developers of BSD, I'm guessing they might have been happier if that company contributed (some of) their changes back. Or maybe a few bucks from the billions of dollars they made.
BSD license basically gave the company to screw everyone else, both end users and original developers. Only a free software license such as GPL protects them both.
> make the code more resistant to forks, esp. less free
GPL doesn't have any restriction on forks. At all. Re-licensing and forking are orthogonal concepts.
> opens an option for the original author of code to do dual-licensing
That doesn't have anything to do with GPL itself.
> provides an opportunity for the authors to prevent certain uses of the code
It guarantees that four freedoms mentioned in the above link are protected.