I still kinda like the restrictive takes of copyfarleft that prevents for-profit entities to use anything without contributions. Workers, co-ops, nonprofits do not have any of those restrictions.
My biggest issues with those licenses are specifically that they are & never could be GPL-compatible which would encourage permissive licenses for libraries which is part of what both license types want to avoid.
Has anyone gone so far as to dual-license under copyleft & copyfarleft?
Man, people do love arguing about words without providing (or looking up) their definitions.
Does the GPL being non "restrictive" mean I can use GPL code in my proprietary software? What word that doesn't offend you should I use to describe this fact?
This is as useless as the git main/master branch debate a while ago.
What word that doesn’t offend you should I use to describe this fact?
Conditional, as in you are free to incorporate the GPL code into your work on the condition that you preserve the freedoms downstream. By default you have no rights to distribute; the GPL does not take anything away, but it grants conditional rights. A restrictive license, like your proprietary EULA, would take away rights that the user would normally have.
Whether or not proprietary EULA's are enforceable is a matter of dispute; see Software user's rights (D. J. Bernstein). Regardless, as Bernstein notes, this default set of rights does not include distribution, which is governed by copyright law. Free software licenses such as the GPL are copyright licenses and grant limited rights of distribution. Note that even most "permissive" licenses are by definition conditional as they include at least the requirement for attribution.
Note that even most “permissive” licenses are by definition conditional
You do realize the whole discussion is about what terms to use for differentiating between GPL-like "restrictive" licenses and BSD-like "permissive" ones? Saying that both are "conditional" really doesn't help anyone.
(also "by definition" the license's grants may be "conditional", not the license itself - it's not as if it looses validity under some condition)
The problem with a copyleft license is it’s hard to make a commercial software open source because a competitor can simply copy your work and sell it for cheaper.
I know. It’s obviously better for the consumer, but it makes it harder to base your business around it, as noted in that article.
So if I want to build a business, I have to look for libraries that are not copy left, and if I want businesses to use my software, I should not license my software as copy left.
That's true of any free software license, and as far as I know most formerly-free fauxpen source projects were licensed under a permissive license, because the intent was to be "business friendly" open source projects.
In fact, copyleft actually has an advantage here; other members of the community can sell your work, but they are also required to respect the copyleft. Stronger copyleft licenses like the Affero GPL even protect against proprietarizing free software as a "cloud" service, but "business friendly" projects don't want it.
Makes sense because if you want to make freely available code but want to allow commercial projects to use it you want to use a liberal license because if your code is copy left licensed businesses won’t want to use it.
I’ve seen this in action: I’ve seen a business reject working with one research group because their code was copyleft licensed, so instead they turned to another group offering a liberally licensed competitor.