Campaign video to stop games from being destroyed! It's being done in a few ways, owners of the game "The Crew" can help especially. There are more worldwi...
Agreed, those are pretty permissive licenses (though not completely free), but they’re still licenses that you deliberately choose, not ones that were forced upon you.
Copyleft licenses do force you to do certain things, like make your changes to the code available, and AGPL was made specifically to patch some GPL loopholes. They are technically less free than something like Apache which is essentially “do whatever you want, IDC…”
As far as I understand, you only have to make your changes to the code available to users of your software. You are free to make any modifications as long as you keep them to yourself and don’t share the binaries (or access the service, in case of AGPL) with anyone. I might be mistaken, though.
Ah I get what you mean, I used to share your same view. I used to think that the MIT license was more free than GPL for the reasons you mentioned.
When Google started working on Fuchsia OS and they said it will be MIT license, I started to get worried that smart products producers would start using it instead of Linux. Then they wouldn’t need to release the source code to customers as the software would no longer be GPL.
The difference is that MIT gives more freedom to the producers, while GPL gives more freedom to the consumers.
Personally, my sympathy goes to consumers, not producers, thus I understood why people say GPL is more free than say Apache or MIT.
Licenses such as MIT, Apache, MPL, etc… are a double-edged sword. 😬
Agreed, those are pretty permissive licenses (though not completely free), but they’re still licenses that you deliberately choose, not ones that were forced upon you.
Copyright is a law forced upon us. It is not some sort of natural state.
So are murder and traffic laws.
In what way are they not completly free? Cuz you gotta keep the same license?
Copyleft licenses do force you to do certain things, like make your changes to the code available, and AGPL was made specifically to patch some GPL loopholes. They are technically less free than something like Apache which is essentially “do whatever you want, IDC…”
As far as I understand, you only have to make your changes to the code available to users of your software. You are free to make any modifications as long as you keep them to yourself and don’t share the binaries (or access the service, in case of AGPL) with anyone. I might be mistaken, though.
You’re correct, but the point is that it’s forcing you to do something. I’m not saying that’s a bad thing, but it is less free than Apache or MPL
Ah I get what you mean, I used to share your same view. I used to think that the MIT license was more free than GPL for the reasons you mentioned.
When Google started working on Fuchsia OS and they said it will be MIT license, I started to get worried that smart products producers would start using it instead of Linux. Then they wouldn’t need to release the source code to customers as the software would no longer be GPL.
The difference is that MIT gives more freedom to the producers, while GPL gives more freedom to the consumers.
Personally, my sympathy goes to consumers, not producers, thus I understood why people say GPL is more free than say Apache or MIT.
Licenses such as MIT, Apache, MPL, etc… are a double-edged sword. 😬