| ▲ | imtringued 16 hours ago | |
I personally find it questionable when people argue that the GPL/AGPL is less free because of the code sharing requirement. On the Rust subreddit you can see people make arguments that can essentially be paraphrased as "Get a real job". Somehow the people selling primary energy, food and raw materials are allowed to make money, the hardware manufacturers to run the code on are allowed to make money, cloud providers to run code on are allowed to make money, people using your software in their business are allowed to make money and even people who have been hired at a company to submit patches and pull requests to contribute to your project are allowed to make money but you, the original maintainer/developer who kick-started the project and paid the initial investment? Suddenly you're no longer allowed to make money. You're expected to work a "real job" (see list above). You're supposed to spend time not working on the project to earn enough money so you can donate your time and money to work on the project to people who most likely couldn't care less about you and your sacrifice and since it is just plain business sense to minimize costs, you should do the same and stop working on the project. The strangest part by far is that if you'd you made your code proprietary from the get go, there wouldn't be any complaints about your GPL code not being free enough. It's a surprisingly pro proprietary code stance. | ||
| ▲ | duskdozer 15 hours ago | parent [-] | |
I don't think it's strange at all - the "pure freedom" licenses intentionally don't have safeguards against exploitation of the system, which attracts those who want to take but not give back, which lines up well with proprietary software. | ||