>>891
>Is there a license that is close to BSD with the differences that commercial companies are not allowed to use the code?
That would not be a Free as in Freedom license though.
(((Ken Silverman))) did exactly that with the Build Engine and now any source port that's based on his code cannot be included in any Free package repository. Don't be a kike, anon. Either be a cuck and give your word away with no strings attached, or be a chad and demand that those who make you of the freedom you give them also pass on that same freedom on to others.
>>894
As I said, it's only for code that I don't care about. Any code you write and put out is proprietary by default, so you have to explicitly give it a license. When it comes to some hacked together shell script of Vim plugin I don't see any commercial value in it, so I might as well give it the most cucked license. A year from now I might not even be using the code anymore, but someone else might find it useful, so I want as few strings attached.
> That way if lawyers in a corporation get uneasy about using public domain, you can tell them that for the small price of 1000USD you are willing to sell them a commercial license, if GPL is too restrictive for them.
But if I do see value in it, why even have a dual license as public domain? That's the sort of thing that should be exclusively GPL with maybe an option to sell an exception for six gorillion sheckels.