Earlier quoted context omitted.
> If some wants to use it in proprietary software they cannot, because if they did they would be unable to then share it with their neighbor. So he isn't free to do what he wishes with the software. Free is one of the most overloaded words in the English language, and I know that at least some of the Free Software movement agrees due to the prevalence of libre software (as if switching to French somehow makes it more…
The problem is people attack the GPL hold up the BSD as if it's without restrictions. But it is (granted, the restrictions are fairly simple to address, their are restrictions places on you, and if you don't follow them, you are in the same boat as the GPL). > There is no free with restrictions In this case, the only option is to write it yourself, as even things put into the public domain can have a catch (Actually,…
This is, by definition, untrue: If something is in the public domain, it is without an owner. It is unowned. Anybody can do anything they want with it, including using it in proprietary software for money and passing it off as their own work. (Assuming nobody is enforcing a code that bans plagiarism, which is totally orthogonal to copyright.)
If there is a catch, then the work is not in the public domain at all. Being owned by someone but released under a liberal license does not put something into the public domain, as the work is still under copyright.
In short: Public domain vs. copyrighted is a binary distinction. 'Freedom' is a continuum on multiple axes.