6 ms·
> The idea that organisations 'owe' the community copyleft software is therefore a bit foreign to me. What do you mean? That is the very credo of free software
by pron 11y ago
> The idea that organisations 'owe' the community copyleft software is therefore a bit foreign to me.
What do you mean? That is the very credo of free software, namely all software should be free. Hence, everybody owes the community free software. You might not agree with it, but that's the ideology behind free software.
> Google and the Android platform has equally went out of the way to isolate the platform from the effects of the GPL.
That's absolutely true. That effort is why Google didn't use OpenJDK (which is under the GPL), which led to Oracle suing them. All because Google went to extreme great lengths to avoid the GPL (they did have their reasons: they believed, perhaps rightly so, that phone manufacturers would not agree to a GPL platform).
- Flimm 11y agoI think the credo of free software is the developers owe their users free software, not the community at large. It's a subtle distinction.
- anon1385 11y agoI'm not sure that is the credo. At least, it's not the credo behind the GPL. Every day I use software that is at least partly GPL code, but I can't access the source code. Why? Because I used a webapp. If the software you use is running on a server rather than your local machine then the GPL says you don't get to have 'freedom'. So "users" isn't a useful distinction when it comes to Free Software, because the GPL doesn't guarantee freedom for users. It only guarantees freedom for the person who owns and controls the hardware.
- Flimm 11y agoGood point. That's more precise summary of their credo and it's narrower than the "community".
- pron 11y agoWhen the GPL was written, this kind of software wasn't very common. Now that it is, the FSP formalized the AGPL, which they recommend over the GPL for server-side software.
- anon1385 11y agoNearly any software is potentially server side software. So really they should recommend AGPL for everything, and relicence all FSF owned projects as AGPL. They don't because a lot of people even inside the FOSS community are violently opposed to the AGPL. Quite a few people think that it conflicts with Freedom Zero.
- shiggerino 11y agoThere is no meaningful distinction between user and developer. All developers are users, and in cases like this, with compilers, all users are also developers.
- fauigerzigerk 11y agoHence, everybody owes the community free software. I think the credo is that developers owe the users of their software certain privileges, like access to source code and the right to modify and redistribute that source code. What I don't like about the way the free software movement demands these rights is the misuse of the words freedom and liberty. By using these words, they deliberately imply that withholding these privileges from users is tantamount to a human rights violation. I think that is an insult to people suffering from real human rights violations.
- pron 11y agoIdeologies are not binary -- they each have relative importance. I don't think for a second that the FSF places software freedom above human rights or even equates the two. You can be a staunch theft opponent; that doesn't mean you believe theft is tantamount to murder.
- fauigerzigerk 11y agoThe wording they use equates the two and I don't think that is an accident. Either they believe it or they use it for effect, just like the media industry likes to call copyright violations theft.
- Retra 11y agoI don't see how you can imply a human rights violation. "Human rights" are a largely technical term. It's not just rights that humans have, it's a special category of restrictions, and unless you point out the significance of that, you're not talking about human rights. The term "Human Rights" is not very good because it invites confusion. This is not the FSF's fault. But you can't go from "you have rights" to "that's a claim of Human Rights." You are imagining what people think and being offended by it, which is your own fault.
- fauigerzigerk 11y ago>I don't see how you can imply a human rights violation By using words that are closely associated with that context. This particular article goes even further, using words usually reserved for humans (or animals) to talk about software itself: "[...] Objective-C was liberated. [...] when and how programming language software is liberated. [...] keep the core operating system of Android liberated." >But you can't go from "you have rights" to "that's a claim of Human Rights." And I did not. I specifically complained about the misuse of the terms "freedom" and "liberty". I have no problems with "rights". Quite the contrary, I value my rights as a user of open source software. But they are different, less important, rights than my fundamental human rights like freedom and liberty. >You are imagining what people think [...] Well, you know, that's the only thing language can ever do. Make people imagine what you think. [Edit] Apparently I'm not imagining too much. Richard Stallman himself says it very clearly here: https://fsfe.org/freesoftware/transcripts/rms-fs-2006-03-09.en.html https://fsfe.org/freesoftware/transcripts/rms-fs-2006-03-09....
- zak_mc_kracken 11y agoThe reason why Google went with writing their own version of Java has nothing to do with avoiding the GPL and everything to do with avoiding to have to pay money to Sun.
- pron 11y agoWell, they had two options: license Sun's Java or do as they please with the GPLed OpenJDK. If they'd chosen the latter they wouldn't have needed to pay a dime. Sun/Oracle place no restrictions in addition to the GPL itself when it comes to OpenJDK (in fact, the GPL explicitly prohibits any such further restrictions). You can do as you will with it.
- wstrange 11y agoMy understanding was that Sun (and now Oracle) had "field of use" restrictions on the JDK that prohibited it being used on mobile devices without buying a license. I am not sure how enforceable those restrictions were, but I imagine that factored into the decision to use the Apache JDK project
- pron 11y agoThat was before OpenJDK. There are a few ways you can license Java. You may freely implement it yourself, but then you must pass the TCK and abide by Oracle's field-of-use restrictions, you may negotiate a license from Oracle (Sun at the time) for their source code and use of the technology, or you can do whatever you like with OpenJDK (although to use the Java trademark you probably need to conform to some other requirements)[1]. BTW, Oracle/Sun's JDK is OpenJDK with a few advanced monitoring/profiling add-ons. In any case, OpenJDK was released in May 2007, and Android unveiled in November later that year and made available only a year later. The reason Google used Apache Harmony was because they couldn't reach a licensing agreement with Sun and chose not to use OpenJDK because of its GPL license, believing phone vendors would reject it. As Google probably wanted to have a non-standard edition of Java, it's unlikely that Sun would have licensed it to them (or they would have required a new standard being formalized first). Their best option was to use OpenJDK, but they didn't. They wrote their own runtime -- which, to this day, is at a great performance disadvantage compared to OpenJDK -- suffers annoying incompatibilities and is a few Java versions behind, all in order to not use GPL software. Was Google right in thinking that phone manufacturers not have put up with GPL? I'm sure that at the time that's what the phone makers told them. Perhaps Android wouldn't have taken off if they had tried to shove the GPL down their throats. But I believe that with the iPhone breathing down their necks and no better alternative, the phone vendors would have yielded. We would have ended up not only with a much better, faster, more compatible Android, but with the most ubiquitous operating system on the planet being truly free. This also would have prevented the Oracle-Google lawsuit. Instead, we're left with a slow OS that's years behind embedded Java, not truly open (as closed-source modifications are made by vendors), and a legal battle that some believe may have far-reaching consequences. All because people are afraid of the GPL. [1]: For example, I believe (though I'm not sure) that IBM's and Aicas's JDKs follow the first choice (maybe the second), Azul's Zing JVM the second, and Azul's Zulu the third.