Earlier quoted context omitted.
Open Source is just the free-but-profitable trend that OP is talking about taken to the limit. It's software that developers make for free and release for free—most often under a license that requires nothing but attribution. Then a not insignificant portion of those developers feel entitled to be paid for their work, preferably at something north of the median salary in their native country. If you're developing ope…
> If you're developing open source software because you believe in the commons, license it under (A)GPL to ensure the propagation of the commons. If you're developing open source because it looks good on a resume, then you've already been paid for it in reputation. But if you're developing open source because you think you'll get paid for it, I don't know what to tell you except that that is not how the world works.…
Fair, but in that case your compensation is choosing a license that gets you acceptance in the community that you're working with.
I'm not in favor of regulating that people who put stuff out into the world for free should get paid for that work, unless we're talking straight up UBI for everyone. If you want government to fund open source, it should do so by employing people to work on open source or by funding everyone to work on their hobbies via something like UBI.
And absent government funding, if you want to get paid you need to have a business model that allows for that. The existing practice in portions of the open source community is to put things out with extremely permissive licenses but then throw a fit when people don't pay you for them. This is what's known as a bait and switch.