I think the distinction between "download and run" software vs. "libraries used to build new programs" should always be stated in this GPL vs. not discussion. For "download and run" software, having it be GPL IMO doesn't limit too much who will ultimately be using your software. But if you are writing a programming library that would be used to create new software, GPL and even the LGPL will scare away a lot of comme…
For me it's rather simple. I like GNU/Linux, the whole free/sharing ecosystem helped me learn so much, it allowed me great productivity, to modify anything and everything, etc. I like others to have the same opportunity, so GPL it is, even for libraries.
My Personal Journey from MIT to GPL
331–340 of 431 posts
Re: My Personal Journey from MIT to GPL
#332Earlier quoted context omitted.
I feel this is a bit of exaggeration. You are copying someone else's work without complying with their license. That act, not the fact that it is GPL, is exposing yourself to unknown amount of legal risk. Legal system does have nonlinear penalty system but at the same time, judgments are expected to be reasonable and fair. Courts will not force you to GPL your code, but they may stop you from distributing your work -…
> You are copying someone else's work without complying with their license. That act, not the fact that it is GPL Right, so the correct conclusion is to never use, never contribute to and never write GPL-licensed software. Then you comply 100% with GPL, you have no legal risk and you also have money to pay for your Gatorade. In fact the best solution would just be to completely rid ourselves of GPL?
Of course, then there's patents. You might want to avoid having any ideas at all.
Re: My Personal Journey from MIT to GPL
#333Earlier quoted context omitted.
If I make a movie and include your copyrighted song for just three minutes of the intro, my whole movie violates the law. Or if I write a book and copy-paste just one chapter you wrote on your blog into it, the book also violated your copyright. And I "starve to death and die" because yes, in this world you can't just take things that other people have made and use them in whatever way you like -- if you can't obey t…
Except that analogy doesn't quite work. If you use a copyrighted song in a movie, you can choose to license that song (and the terms of use and cost will be up to the rights holder) -- licensing that song doesn't give the rights holder reciprocal access to your film. So yes, I agree with you that you need to obey the terms someone else has used for their work, or else you shouldn't use the work -- but your analogy wi…
Re: My Personal Journey from MIT to GPL
#334MIT-like freedom is the "freedom to sell yourself as a slave". GPL is "your liberty ends where my nose begins". If you understand freedom as the removal of social constraints, you won't understand the value of something like GPL software or Wikipedia. If, on the other side, you think of freedom as the capability to do things, the accumulation of knowledge in copyleft projects creates possibilities that are less likel…
> MIT-like freedom is the "freedom to sell yourself as a slave". I don't think this analogy is strictly wrong , but the tone is insensitive enough that it is unlikely to be persuasive to the people you are trying to persuade. (Also, some will feel that it diminishes the gravity of actual slavery.) I agree with your point, but I think you would be better off stating it in a different way.
I copied it here to deliver the basic idea as fast as I could, but it certainly is out of context as the starter of a calm conversation with more time to expose ideas and ponder them, as is the style of this forum.
Re: My Personal Journey from MIT to GPL
#335Earlier 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.
What? I'm really struggling to find the nugget of 'point' in there, but... what? Are you saying that Gravity is somehow biased toward powerful people? Are you saying that refraction is somehow biased toward powerful people? I'm left so confused by your comment. It's amazing -- hopefully in a good way!)
Re: My Personal Journey from MIT to GPL
#336Earlier quoted context omitted.
You did a switch-a-roo between the perspective of individual programmers to the perspective of organizations that produce software, and I think that doing so muddies the situation a bit. Whether programmers sell their code or their time doesn't seem that important to me. (I've seen it work out both ways.) What is more important to me is what they're paid in. Personally, I like to get paid in money, because I can easi…
> You did a switch-a-roo between the perspective of individual programmers to the perspective of organizations that produce software, and I think that doing so muddies the situation a bit. The comment I replied to talked about programmers, and I was also talking about programmers, so ... where did I supposedly do that? > Personally, I like to get paid in money, because I can easily turn money into things like food an…
Directly, not at all. But most companies find it very difficult to turn a profit on GPL-licensed software without resorting to things that render the whole thing moot, like being SAAS vendors who never "distribute" the software in the first place. The whole "derivative works" angle on the GPL, then, makes it hard for commercial vendors to make distributable software that relies on GPL packages without putting their own revenue stream at great peril.
So commercial software shops tend to build on MIT, BSD or Apache licensed stuff. Which is typically NBD. My experience has been that fears about "not contributing back" are typically unfounded. Everyone submits pull requests for their bugfixes and enhancements, because nobody wants to deal with maintaining some special snowflake private version of cURL or whatever.
Consequently, I think that the elephant in the room is that, typically, when people complain that there's something akin to a moral obligation to use GPL, what it's really about is fears that someone might make more money than they think is seemly by shipping closed-source software that relies on open-source components. Which, fine, if you don't like that, you do you and license the software however you want. But don't begrudge the rest of us for not being quite so worried about that.
As far as the whole ownership thing goes, I'd say it was pretty clearly implied in your first sentence:
> The programmer doesn't sell code, the programmer sells time writing software. With proprietary software, the owner of that software has a monopoly on the work on that software
That statement tacitly denies the existence of freelance software developers, by implying that all programmers are working for another company for some sort of salary or wage, and don't ever individually own code themselves. Which isn't quite true, and subtly frames things in a way that strips developers of their moral agency.
Re: My Personal Journey from MIT to GPL
#337Earlier quoted context omitted.
Redistribution doesn't mean public. I've worked for years extending A/LGPL code that we redistributed, yet much of it never saw the light of day, since our clients have no interest in publishing it (although they are free to do so, of course).
You’re essentially working as contractors for the company in that case though. So you’re effectively part of the company and aren’t really distributing as the term is generally understood. Of course there is some ambiguity as there always is.
Re: My Personal Journey from MIT to GPL
#338Earlier quoted context omitted.
Is this meaningfully different from being able to build a multi-billion dollar company like Red Hat on top of other people’s GPLed work? Yes, because of the GPL, they have to give RHEL customers the source to all their patches, but what difference does this make in practice?
> but what difference does this make in practice? CentOS is the difference; it is one of the most widely used distributions has the same stability and longevity characteristics and gets security fixes just as fast as RHEL.
Re: My Personal Journey from MIT to GPL
#339Earlier quoted context omitted.
> It enriches everyone, even those who I don't necessarily agree with. That's definitely a valid PoV, but you just have to realize/accept that it may empower people who have power over you. I'm mostly talking about economic power here, but with the absurd expansion of lobbying, etc., this may extend to political power, cf. Turbotax[1]. Again: It's ultimately up to you, but for me... I don't want to give big conglomer…
> I think BSD (permissive for developers, maybe restrictive for users) vs. GPL (restrictive for developers, permissive for users) is very similar to the Paradox of Tolerance in a way. It very much boils down to tolerance, yeah. I've made the experience that in the communities where permissive licenses are common, there is much larger tolerance for proprietary software and services than in communities that revolve aro…
Re: My Personal Journey from MIT to GPL
#340I spend a lot of time and effort on my code, and I don't mind sharing it for free. I would prefer if other people tuned into that mindset rather than greedily raping the world for profit.
But adding more rules never seem to help, it always causes more division.
My current perspective is that its simply not my responsibility to push others into doing what I believe is the right thing.
Which is why g-fu [0] is released as MIT.