4 ms·
And I prefer my software to remain open no matter who works on it or distributes it. So, I use GPL. Amazing how people can have different priorities and differ
by SwellJoe 16y ago
And I prefer my software to remain open no matter who works on it or distributes it. So, I use GPL.
Amazing how people can have different priorities and different beliefs. (And, amazing how one can abuse the word "free" or "open" in either case to mean two very different things.)
- protomyth 16y ago> amazing how one can abuse the word "free" or "open" in > either case to mean two very different things It seems to happen a lot in technology and the naming of bills in congress. It has got to the point where I start to ignore the words. "Net Neutrality" is the latest phrase that has a lot of meanings depending on who you talk to, but has no actual technical or judicial meaning. I could accept a technical definition that has a meaning, but not this two word label that doesn't. For example, if I said "I was against port blocking or banning protocols except by the end user", it has some meaning. My definition of these weasel words (tis a shame open and free are among them) is if someone says the phrase "I support X" and it gives me no real knowledge of their actual beliefs.
- dwc 16y ago> And I prefer my software to remain open no matter who works on it or distributes it. So, I use GPL. BSD license accomplishes that just fine. BSD licensed code has been taken, extended, modified and used in proprietary products for decades, and yet the original contribution remains open. I think that what you object to is that someone can take your code and make money using it in a closed source project, perhaps modifying it in the process. If that makes you unhappy then GPL will serve your desires better. But saying a BSD license won't keep your code open is not true. It may seem like a nit, but it's one that matters.
- wvenable 16y agoIt depends on how you define "open". For Stallman, one of the main goals of free software is the ability to get into your software and be able to fix bugs and port it to other platforms -- it all started with RMS getting stuck with a proprietary printer driver. All that BSD code that's been taken, extended, modified and used in proprietary products is no longer open. You can't get into OS X and fix bugs or port it to another platform. So even if the original code is still open, other distributions of that same code are not.
- bad_user 16y agoThat doesn't stop people from buying OSX or Windows, and you're saying it as if OSX couldn't have happened if it wasn't for the freebies they've incorporated. Funny thing the Linux kernel came from a man that doesn't even buy RMS's propaganda, and that used GPL just because he was looking for some ROI.
- dwc 16y agoYou are correct: the original code (and ongoing work based on it) is still open, and Apple, et al, versions are not. This is fine. First and most importantly, because the desire to share code with BSD comes with no strings attached. It's just the desire to share. You don't have to have the same beliefs and priorities as I do in order to use my code. I believe in freedom enough to give you all the freedoms to do as you like with my code, and you don't have to behave in ways I see as good. Secondly, if Apple were unable to use BSD code then what would happen? They would go completely proprietary, that's what. For them the alternative is not between BSD and GPL! Would the user be better served, or worse? As it stands, Apple contributes some things back to open/free projects, and a big part of that is due to their ties to BSD code. Thirdly, with OS X as it is, or if Apple had not taken BSD code, or Apple did not even exist, would a user be more able or less able to run FreeBSD? No. Or GNU/Linux? Again, no. Stallman and the FSF think that they're making a difference with licenses. But I think the truth may be that it's not the license that's really the movement. The movement is collaboration on a global scale and sharing code and making cool things for everyone to use. The licenses do not drive this. In the end we have to make sure that licenses serve our purpose rather than the other way around.
- wvenable 16y ago> This is fine. But not for RMS since it doesn't address the founding concern of the FSF! You sort of glossed over that. If you write BSD code, and it gets put into OS X, your ability to tinker with your own code in that context is gone. I don't think you can clearly claim one license here is more free than the other -- they're both securing different kinds of freedom.
- 16y ago
- cabalamat 16y ago>> And I prefer my software to remain open no matter who works on it or distributes it. So, I use GPL. > BSD license accomplishes that just fine. BSD licensed code has been taken, extended, modified and used in proprietary products for decades, and yet the original contribution remains open. But the modifications might not do, which is what GPL proponents care about. To me, the GPL is like saying "I'll share with you, if you share (your changes) with me". This is not to say that GPL is better than BSD, or that either is better that a proprietory license; they're each designed to do different things. One might as well argue about whether a car a plane or a boat is the best form of transport.
- dwc 16y ago> But the modifications might not do, which is what GPL proponents care about. To me, the GPL is like saying "I'll share with you, if you share (your changes) with me". Yes, that's correct. It's not about better or worse at all. It's about a license that fits what you want, as a developer. Sometimes it varies by project! For instance, a developer who normally uses GPL may choose BSD for a reference implementation of a client program using their API, specifically because commercial products could incorporate the code.
- kemiller 16y agoI just wish someone would give Stallman the memo.
- moron4hire 16y agoBut how can I possibly close your software? I can't stop you from distributing your library in the original form that you created it in. So your software will always be free, regardless of whether or not I abide by the GPL.
- brudgers 16y ago>"I prefer my software to remain open no matter who works on it or distributes it. So, I use GPL." There are other licenses which will insure that your software remains free and open. GPL requires that mine become free and open as well...and that's fine in so far as it goes. Structurally, however, the copyleft movement only works so long as there is a system of copyright protections, powerful institutions for enforcing them, and the threat of severe sanctions for violating them. In other words, the copyleft movement is built on the same foundation as its antithesis. Both copyright and copyleft depend on the author's right to restrict future use.
- jackolas 16y agoWhich is why its been fairly successful.
- bonch 16y agoYour software would still be open under a BSD license. Using it in a closed-source project doesn't automatically remove the existence of the open source version.
- bad_user 16y agoFree as in MySQL and Java?