6 ms·
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
by jasonlotito 16y ago
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, I think their is a license that basically does with you'd think putting something into the pubic domain does, I just forget the name).
So basically...
> So he isn't free to do what he wishes with the software.
This is true of pretty much all licensed code, including BSD.
- jedsmith 16y ago> (Actually, I think their is a license that basically does with you'd think putting something into the pubic domain does, I just forget the name). CC0? https://creativecommons.org/choose/zero/ https://creativecommons.org/choose/zero/ > This is true of pretty much all licensed code, including BSD. Couldn't agree more. Don't call it Free, and don't try to associate Free with the GPL at the expense of everything else (which seems to be the push). Libre too. Because if anything, the GPL is more restrictive than alternative licenses. That's my gripe.
- rick888 16y agoSometimes I almost feel like Stallman intentionally used the word 'free' in the license to confuse people. Many people think that it means you can do whatever you want with it and get in legal trouble down the line. This is why I won't use any GPLd libraries in any of my projects. It's too risky.
- jasonlotito 16y agoI believe it's: http://creativecommons.org/publicdomain/mark/1.0/ http://creativecommons.org/publicdomain/mark/1.0/ though I don't really remember. > the GPL is more restrictive than alternative licenses. So, you don't like the GPL. That's fair. However, not everyone has the same goals as you. Your main contention at the start, if I understood you correct, was that, we should be sharing and not repeating ourselves. I write something, publish it, share it, and you should be able to use it for your project without having to worry about licenses. And you see that as more free then with licenses that have arduous restrictions, like the GPL (Because, while the BSD does have restrictions, they are fairly easy to overcome). If I'm wrong with your overall view here, apologies. Essentially, you want what people who use the GPL want: a community of sharing. You want it via choice, GPL users want it enforced. And that's where GPL users see the value in a license: they help push your agenda. So while BSD gives other people more freedom to do what they want with the code, it does nothing directly to push people toward that way of thinking. My personal opinion is it's all fairly annoying. I just want to program. =)
- derleth 16y ago> as even things put into the public domain can have a catch 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.
- jasonlotito 16y agoIt's my understanding that in the past, things have lapsed into the public domain as copyright expired. However, laws changed, and these public domain items were put back under copyright protection. I cannot remember where I read it, or under what context. That being said, what I said was, afaik, incorrect. If something is specially put into the public domain, it's there. The things I read about weren't explicitly put into the public domain by the copyright owner. They just fell out of copyright. My apologies.