If “theft” is your only concern yes. It’s a common misconception that copyleft licenses stops rich companies from stealing. It does not.
I am more concerned about societal enrichment vs corporate enrichment.
If you release some code under MIT that a company finds useful, they could take it, improve it a bit, and resell it back to the community. This enriches the company at the expense of the community. Without the original code the company could have never taken it as a basis to sell and the community that wrote the code gets nothing.
If you release that same code as AGPL the company can take it, improve it and sell it to the community. BUT the difference is that the community now benefits from those improvements too. Maybe more improvements happen. Maybe a second company takes those improvements and sells them too. The community would have all the improvements and would benefit from greater competition.
With copy left licenses. The community is enriched and companies are enriched.
With MIT style licenses. Companies are enriched at the expense of the community.
@mholiv@lemmy.world It looks you believe that magic letters G, P and L make company release their improvements to the public. Actually they do the same with MIT and GPL code: include it into closed source products and that is. Because there’s no way for you to check if there was GPL in closed source program.
But the GPL style licences bring licence compatibility issues while MIT style do not. (And that’s why Linux cannot include ZFS driver despite it’s being “GPL style” licenced)
If “theft” is your only concern yes. It’s a common misconception that copyleft licenses stops rich companies from stealing. It does not.
I am more concerned about societal enrichment vs corporate enrichment.
If you release some code under MIT that a company finds useful, they could take it, improve it a bit, and resell it back to the community. This enriches the company at the expense of the community. Without the original code the company could have never taken it as a basis to sell and the community that wrote the code gets nothing.
If you release that same code as AGPL the company can take it, improve it and sell it to the community. BUT the difference is that the community now benefits from those improvements too. Maybe more improvements happen. Maybe a second company takes those improvements and sells them too. The community would have all the improvements and would benefit from greater competition.
With copy left licenses. The community is enriched and companies are enriched.
With MIT style licenses. Companies are enriched at the expense of the community.
@mholiv@lemmy.world It looks you believe that magic letters G, P and L make company release their improvements to the public. Actually they do the same with MIT and GPL code: include it into closed source products and that is. Because there’s no way for you to check if there was GPL in closed source program.
But the GPL style licences bring licence compatibility issues while MIT style do not. (And that’s why Linux cannot include ZFS driver despite it’s being “GPL style” licenced)