Earlier quoted context omitted.
Well, right. Thats my point. They have enough parts in "Android" which don't fall under GPL and thus they can keep them proprietary.
"the GPL is ineffective because the non-GPL parts become proprietary" doesn't seem like a strong argument against the superiority of the GPL.
My Personal Journey from MIT to GPL
391–400 of 431 posts
Re: My Personal Journey from MIT to GPL
#392Earlier quoted context omitted.
And no true Spartan... Some schools of thought use some weird notion of freedom to derive some abstract structure that has never been tried anywhere and claim it has some hypothetical properties. You want to call that "true capitalism". I like theory, I do theory, but the post was talking about existing social systems within which we operate. Your private definition of "true capitalism" has nothing to do with that sy…
If state capitalism is capitalism, then National-socialism is socialism.
Re: My Personal Journey from MIT to GPL
#393Earlier quoted context omitted.
Just because that one thing happens to not be entirely worthless, doesn't mean that anything has value. Also, since you're not even a professional developer, I'm not directing that advice at you.
> Also, since you're not even a professional developer, I'm not directing that advice at you. I think your implicit assumption that most Github projects are created as a form of resumé building is incorrect.
If that doesn't apply or matter to you, that's fine. You can move right along.
Re: My Personal Journey from MIT to GPL
#394Earlier quoted context omitted.
> [...] We had to either go GPL v2+, which assumes the FSF will never go crazy, [...] This is a rather common common misconception. If you use the "Version 2 of the GPL or any later version"-clause in your specific GPL licensing lingo, then any re-distributor may CHOOSE to distribute under GPLv3, or GPLv4 (if it ever exists), or, for that matter, also GPLv2. You're not bound to re-distribute under GPLv${latest} becau…
A future GPL v4 could say "Your code can be converted to the MIT license", or even "your code can be used by company X" in the event of a takeover (which I don't consider an impossible option).
The FSF is a tax-exempt 501(c)(3) charity; if it would institute policies to benefit a single for-profit entity, the inevitable IRS audit would be excruciatingly painful and likely result in jail time for directors.
Re: My Personal Journey from MIT to GPL
#395That is restrictive on developers, but that's just the cost of doing business here. If you don't share those ideals, that you should be able to inspect and alter the source of the code you run, you will likely never "understand" GPL.
Re: My Personal Journey from MIT to GPL
#396Earlier quoted context omitted.
> I was very disheartened to see the Linux community's and other GPL projects' attitude to enforcement actions brought by individuals. Can you share some examples of what's happened that's disheartening? I'm assuming based on context that the reaction to individuals enforcing GPL violations have been negative, which I would agree is disheartening. If you don't enforce the terms, the terms are valueless, and you might…
The big case recently was in Germany against VMWare [0]. They lost that case. But it was controversial partly because the person (who contributed a non-trivial amount of networking code) was asking for monetary damages in addition to bringing the company into compliance. But setting the money aside, even the enforcement part was flamed by Torvalds and Greg KH [1]. The gist was that they're able to bring more people i…
https://sfconservancy.org/copyleft-compliance/vmware-lawsuit...
Some years earlier, there were lawsuits brought by Patrick McHardy, who contributed a non-trivial amount of networking code, that asked for monetary damages; these lawsuits were not supported by any organization.
https://sfconservancy.org/blog/2016/jul/19/patrick-mchardy-g...
Re: My Personal Journey from MIT to GPL
#397Earlier quoted context omitted.
> That's definitely a valid PoV, but you just have to realize/accept that it may empower people who have power over you. Newtons Equations has also empowered the powerful for a while now but I think we are still happy that they are available for free for everyone without any limitations.
Nobody can take them, change them and close them and sell you a better version of them. So, I have no idea how you made the connection to MIT here.
Create a better version? Sure. Make the better version closed? Sure.
But close it? No.
Same with math: once discovered and publish anyone can do anything with it.
Re: My Personal Journey from MIT to GPL
#398Earlier quoted context omitted.
The GPL is not self-serving; it is a tool to achieve a type of society, and that is the society you seem to enjoy, too. After all, by what else should be measure the permissive licences vs copyleft licences if not by their influence on society?
Are you one of those "GPL is socialism" people? You are misguided. Yes, there are lots of marxists/communists in the open source / free software community and most people in it lean left. But the GPL itself is compatible with a capitalist society. In fact, GPL can be the basis for making money with FLOSS software, by offering non-GPL'd commercial licenses. All the GPL ensures that if you want to make a proprietary fo…
The idea is that the GPL empowers users to modify and distribute software rather than enforcing a particular structure of developers and users.
Of course the GPL is not a system of government, so these comparisons are mostly "in spirit". In reality, it's a clever hack to give power to users by abusing the capitalist copyright system (which has historically morphed into a tool for corporations to oppress users).
But the GPL is definitely not communist nor socialist because it has no relationship to government intervention at all (other than relying on copyright laws for its strength). Marx had no interest in governments.
Re: My Personal Journey from MIT to GPL
#399Earlier quoted context omitted.
"the GPL is ineffective because the non-GPL parts become proprietary" doesn't seem like a strong argument against the superiority of the GPL.
You are not getting my point. The point was, that the ability of the GPL to enforce source sharing is limited. Where source sharing and redistribution are not desired, GPL licensed software just isn't used. Or used in a way that it does not affect the propriatary parts.
I think "there isn't enough software under the GPL" is not a criticism of the GPL's effectiveness. If anything it supports the GPL as a method for ensuring user freedom.
Re: My Personal Journey from MIT to GPL
#400I feel like where this debate breaks down is in trying to apply the same license to both reusable libraries and finished products. For a library, an MIT license is much more likely to get it adopted in a finished product that is accessible and maintained. A GPLed library can only get adopted in a GPLed project, which means there may be a ton of economic constraints that make the library's functionality inaccessible t…
This distinction is part of the reason why the LGPL exists, and why many libraries are in fact licensed under LGPL instead of GPL.