17 replies
28 recasts
209 reactions
1 reply
0 recast
5 reactions
You're right about the reasons for wanting copyleft (nudge towards openness), but you're wrong that copyleft archives them.
1. Copyleft creates rewrites, not collaboration. There are tons of examples of people rewriting copyleft encumbered code, it's cheap and fast to rewrite just the part you need. I've even done it. There are ~no examples of an existing codebases being relicensed just to adopt a copyleft dependency. If we're lucky, the rewrite is OSS, but that's not the default! I'd go as far as to claim copyleft creates more duplicated proprietary code.
No one wants to maintain a fork if they don't have to, I'd rather upstream a fix and have it be maintained for free. Permissive licenses create more collaboration this way by default. Permissive creates less duplicated code and more OSS.
2. Strong copyleft is asymmetric and exclusionary. Copyright holders have special rights to relicense under different terms that the user/consumer does not have. Many companies ban touching strong copyleft code, and most people work for companies, so you're naturally losing a huge subset of possibly collaborators.
Permissive licenses are symmetric, everyone has the same rights including the author and users.
(Can expand more if you'd like, working on a essay myself.) 1 reply
0 recast
5 reactions
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
1 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
1 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
1 reply
0 recast
0 reaction
