I contributed hundreds of hours of work into libraries. They are used by the same companies that sell me locked-down devices that I cannot modify or even inspect. They even invade the my privacy and I cannot disable that.
At least GPL tries to mitigate this problem. MIT turns volunteering into unpaid labor for some billionaires.
Calling it "far more abstract principle" is quite absurd.
These companies try hard to push the narrative that MIT is "practical" and GPL is "political" - guess why.
However, I'm under no illusion that it'll prevent my unpaid work from being used by billionaires.
Setting aside those people/companies that are willing to violate the AGPL, even the ones that respect it are free to use it as long as they redistribute the source to modifications they make.
Anyone (including billionaires) could do that, and not every business model relies on keeping their source code secret.
There's plenty of evidence that AGPL is reasonably effective at that. SaaS providers are clearly afraid of it.
> not every business model relies on keeping their source code secret.
I was never talking about secrecy and business model.
It's about allowing end users (including myself) to have some reasonable chances to inspect / update / reflash their devices.
The GPL has a different usage definition: run and execute. E.g. think of an image manipulation program under the GPL. If you design a game, you run the program to create assets, but none of the created assets contain a trace of the original program any more. The game you ship doesn't either. The GPL doesn't affect you. However, if you tried copying one of the algorithms implemented in the program into your own proprietary competitor, you infringe on the copyright now.
Anyway, I certainly think the MIT license is political - I also believe in the political position of free education for all people, even if they're billionaires (or children of billionaires), and in the political position that I should be taxed to provide these services for people richer than me. I donate to charities that help people who do not repay me. And so forth.
If some billionaires want to profit off of unpaid labor, don't think you can stop it by using the GPL, which relies on the legal system and copyright laws that made them billionaires in the first place. If you sue them for infringing the GPL, you might have a great strategy to win their game, but you're still playing their game in their courts. There's a saying from a totally different context that applies here too, I think: the master's tools will never dismantle the master's house. We've had the GPL for decades now and the result is there's a lot of billionaires whose fortunes were made via GPL'd software like Linux.
If you want to get rid of billionaires, or of freeloading billionaires, or of locked-down devices, or of invasions of privacy, take action against that thing. Do not fall into the trap of "Something must be done, and the GPL is something."
Um... no? The idea behind MIT/ISC and the like is to let other people use your software, which they aren't automatically allowed to do because copyright is broken by default.
There's a lot of software that I would like to use in my day job that I can't touch because it's GPL. This is by design.
> These companies try hard to push the narrative that MIT is "practical" and GPL is "political" - guess why.
I have no sympathy for FAANG, but that happens to be correct. GPL is explicitly political in its intent.
Good: the license is working as intended.
> I have no sympathy for FAANG, but that happens to be correct. GPL is explicitly political in its intent.
Don't be cheeky. The sentence was [ push the narrative that MIT is "practical" and GPL is "political" ]
The MIT is equally political - just siding with the freeloaders.
It's not different from soldiers taking weapons from the enemy they are fighting. A pretty common tactic.
Fighting fire with fire. Where's the hypocrisy?
What does the endgame look like for an abolitionist?
God forbid people use a license that makes it easier to turn a profit so they don't have to beg to stay afloat.
The “rolling release” model, where the latest version's proprietary but six months ago's version is libre, simply cannot be done with something like MIT unless you're willing to risk somebody else taking it all for themselves.
Can you name an IC that profits from their software with the GPL?
By contrast I know of a very well-known IC that profits (handsomely) from their software with an even looser license than the MIT - SQLite.
This is exactly what happened even when they used AGPL, something that was thought to scare cloud vendors, but instead it wasn't scary enough, so these companies had to invent new proprietary licenses.
Plausible used to be MIT, and exactly this happened to them.
But my day job's fine with me using that software. Why? It's not using the law to restrict people's ability to use their computers when that software is installed.
MIT and the like, while being good open source licences, allow anyone to break the chain and not release their code to the public. So it is good in terms of being open source and free/libre now, but does do anything for the future, and does not do enough to bring about the vision of a fully free world.
Personally, I'd prefer the GPL licenses unless there's an good reason not to.
The idea that there is some wonderful "community" on GitHub and all this code just flows back into a beautiful, better place simply isn't how programming works. No one would do that.
Therefore GPL helps both users and devs.
That is reducing what GPL is about quite a lot.
For example it is equally important, if not more, that modifications in most cases have to be contributed back to the community, which means getting companies to take part in the action, instead of simply using work of others, profitting from it and never contributing anything back.
This is wrong. There is no requirement to contribute back to the community, just the requirement that changes (or rather, the source with your changes) be made available to your users. This means they could mail CDs of their code to their paying customers only, if they so choose. A far cry from "contributing back to the community", closer to something like "a pain in the ass."
The theoretical possibility of charging money for distributing GPL software has not materialized for any company. You can get RHEL for free if you want, for example, and build sell your own devices with it.
If the world stabilized on a few software products that did what people wanted to do, like and office suite, that would be great. No more work needs to be done on it. Just a little maintenance going forward. Like roads. They cost a lot to build, but little to allow someone to drive on them.
All you have to do to comply is make your own source code available on request to users who accept your license, along with installation instructions to build the running product. That's not contributing anything to the other dev's community.
I am not so sure about what you say about releasing it to only paying customers. That might be true. In that case one of the original developers could buy 1 license or the community could pay for 1 license and this way get the source code. Then the developers of the modification would get some pay and the original developers would get the source code.
The GPL only requires you to make the source code accessible to those people who also get the binary from you, not everyone, but most entities just allow downloads for anybody. It's more expensive to implement checking than it's to just allow downloads for everyone. xyzzy_plugh is splitting hairs here.
"Contributing back to the community" sorta implies you're opening a PR, following coding guidelines, writing tests even perhaps. What happens in practice is corps just hack everything together and rush stuff out the door -- no communities want those contributions. It's rare that these sort of releases contain anything novel or useful. Take a look at the OSS releases for Amazon's products (Echo, FireTV) and be prepared to be underwhelmed.
GPL is not necessarily for developers to get productive work done. It is for people to ensure maximum benevolence with their work for everyone and take the highest moral position. I believe what needs market penetration is this ideal, rather than the GPL itself. GPL is for people who already hold this kind of ideal. They are looking for exactly this.
I don't say you shouldn't ever make money from your work or never use any copyright/MIT/BSD licenses. Most people are not filthy rich and need the money. What I am saying is GPL is not for this, and does not have the requirement to be convenient or framed in a different way than the heroic selfless endeavor it is, in any sense.
Try getting some productive work done without the source. Like fixing a printer of a proprietary driver, for instance. No, the GPL is about exactly about getting practical work done. That's why it emphasizes so much on the 4 essential freedoms, and why 3 of those 4 freedoms are essentially the same thing "the freedom to tinker with the source code and share that information with other developers who can tinker with it some more and do the same".
What is the range of opinion regarding the MIT license? From what I’ve seen, people are either fine with it, or mildly disgruntled. Exceptions are rare. And of course, corporations love having access to software libraries under this license.
How about the GPL? Individual developers seem to be either ok with it, or enthusiastically in support. That’s cool—I’m sure we can all relate to those feelings. But a lot of, ahem, for-profit institutions simply will not get involved in GPL-licensed software. We’ve seen repeatedly the effects of their willingness to walk away, to invest in alternatives, etc.
It seems obvious, if depressing, how things will move over time.
I think this is painting the picture in a too one-sided way. Here is another way to see it: While for-profits might develop their own alternatives, they will fail to make those GPL licensed in most cases, because that is what they wanted to avoid: Giving back to the society, that allows them to exist. So they will have proprietary code. The next company will do the same and so on, all while slowly the GPL licensed alternative creeps up on them, until finally it has caught up. It gets ever more expensive to not use GPL software, as free software slowly gains ground.
This seems a naive take when considering that it's Corporations who hold the most Intellectual Property[1] (Patents and Copyrights) and are the 'customers' or beneficiaries of Intellectual Property laws and systems.
It's Corporations who focus on IP acquisition (and thus monopolization) strategies (e.g. Google buying smaller startups to add their Intellectual Property to it's repertoire).
...in other words, the likelyhood of average Joe being helped by the Intellectual Property system to get access to the fruits of his labor is not a common situation at all. Most new innovations are the result of access and engagement with existing Corporate Intellectual Property (plus an expensive education).
Of course, copyleft licenses such as the GPL _can_ be used to protect the authors' rights to compensation for commercial use of their work - but the framing matters. I think that's the fundamental reason open source licenses such as BSD and MIT have caught on - they centre on the need of the developer to get productive work done, not on the far more abstract principle of the home PC user being able to recompile their own software stack from source.