Earlier quoted context omitted.
Arguably allowing your work to be used by anyone except Google is a feature not a bug.
You publish open source code so that others can benefit from it, and if Google uses it maybe billions of people will benefit from it, so I disagree.
The Unlicense is an inferior license wrapped in an atrocious name
21–30 of 185 posts
Re: The Unlicense is an inferior license wrapped in an atrocious name
#22A let is more-or-less lost, as a noun in English, but in the form inlet and outlet it remains ubiquitous. In "let or hindrance" we might observe that a right of travel (a let) might well be a hindrance to other uses of the property.
A let in tennis is so-called because you 'let' the server try again. The sense is clearly one of permission to the player, not hindrance by the net.
Re: The Unlicense is an inferior license wrapped in an atrocious name
#23Re: The Unlicense is an inferior license wrapped in an atrocious name
#24Why do people want public domain software licenses? Just use a proper licence and die at some point. End result is the same without the uncertainty.
Re: The Unlicense is an inferior license wrapped in an atrocious name
#25I like the aspect that people who don't care about copyright have an advantage, and people who have internalized it cannot even use the code privately or look at it. I think it tells that I am not a big fan of the idea of intellectual property...
Re: The Unlicense is an inferior license wrapped in an atrocious name
#26I wish people would get together to agree upon a public domain alike software license that everyone finds acceptable. That'd mean: * OSI approves it * FSF approves it * Google and other companies with large stakes in FOSS find it acceptable * Github + Gitlab support it in their templates Can we have that?
Re: The Unlicense is an inferior license wrapped in an atrocious name
#27I wish people would get together to agree upon a public domain alike software license that everyone finds acceptable. That'd mean: * OSI approves it * FSF approves it * Google and other companies with large stakes in FOSS find it acceptable * Github + Gitlab support it in their templates Can we have that?
Re: The Unlicense is an inferior license wrapped in an atrocious name
#28I'm not contributing to open source projects privately right now. But if I was publishing code on my own, I would probably make it actually unlicensed at first to keep my options open as much as possible. I would just put it somewhere and say: "here is code, you are technically able to look at it, but I am not giving you any permission". If somebody wants to use it and needs to follow copyright (for example in a comm…
I can’t stop you doing that. I’m not sure I even want to. I hate copyright, and while I’m not sure it should be completely destroyed, certainly it should be weakened by — say — ninety percent.
However, that doesn’t mean I’m willing to break it. What I’ve internalised, having seen the alternative, isn’t copyright — it’s the rule of law. I’m not willing to break that just because it’s personally inconvenient.
Re: The Unlicense is an inferior license wrapped in an atrocious name
#29I wish people would get together to agree upon a public domain alike software license that everyone finds acceptable. That'd mean: * OSI approves it * FSF approves it * Google and other companies with large stakes in FOSS find it acceptable * Github + Gitlab support it in their templates Can we have that?
What about LGPL? It seems to tick all of the 4 boxes you have.
Re: The Unlicense is an inferior license wrapped in an atrocious name
#30Why do people want public domain software licenses? Just use a proper licence and die at some point. End result is the same without the uncertainty.