4 ms·
"Oracle’s recent lawsuit against Google and open source" The lawsuit is against Google, not the OpenJDK. It seems disingenuous to keep linking Google's situat
by protomyth 16y ago
"Oracle’s recent lawsuit against Google and open source"
The lawsuit is against Google, not the OpenJDK. It seems disingenuous to keep linking Google's situation with Open Source in general. Google isn't using the OpenJDK. Google didn't want to spend the money and now has to deal with that decision. A simple "We are not going to a conference sponsored by someone suing us" would be good enough. Adobe and Google must have sent their people to the same blog training program.
- ergo98 16y agoIf you attack an open-source project (which the pertinent parts are) with general software patents, how is that not an attack on open source? What Oracle is doing is absolutely no different than what SCO was engaged in. Note that Oracle's general patents on rudimentary VM and runtime characteristics could be applied against any number of non-Java targets. There just aren't many with the pockets as deep as Google.
- masklinn 16y ago> What Oracle is doing is absolutely no different than what SCO was engaged in. SCO asserted ownership of code they didn't own and licenses they didn't have. How is that even remotely similar?
- ergo98 16y agoBoth are extorting open source projects based upon dubious claims. In the SCO case the claim was that Linux consciously or unconsciously borrowed from SCO's purported property because there are superficial similarities. In this case, Oracle is claiming that Android borrowed from their newly gained property because there are superficial similarities to some vague patents which virtually any modern VM runtime runs afoul of. I think the similarity is overwhelmingly obvious, so demanding that I prove that it is "remotely" similar is pretty aggressive and uncalled for.
- patrickaljord 16y ago> Google didn't want to spend the money and now has to deal with that decision. It's not that they didn't want to pay, they wanted to make a fully open source mobile OS. Going with OpenJDK would have forced them to make Android GPL which would have been a no-no for carriers and going with Sun's licensed JVM would have made Android not open source. So Google had to go with their own VM if they wanted to have an open source mobile OS based on Java.
- protomyth 16y agoThey wanted Java, but didn't want OpenJDK or a licensed VM. At that point, I gotta wonder why they didn't pull a Microsoft and pick / develop a different language? They use Python a lot. Buying a license from Sun that allowed for a open vm would have probably worked given how money starved Sun was. /edit/ I should point out I am worried about what other VMs this has implications for and not really liking software patents in the first place (if it can be copyrighted, I don't think it should be patentable).
- jrockway 16y agoWhy would the GPL have been a "no-no" for carriers? Linux is GPL'd, and I'm pretty sure Android uses that. I can't think of a single Android device that doesn't let you install your own build on it. (After some coercing, of course.)
- technomancy 16y ago> Why would the GPL have been a "no-no" for carriers? Because carriers are staggeringly stupid, I think. > I can't think of a single Android device that doesn't let you install your own build on it. I wish that were true: "Unlike the DROID, the Milestone has a bootloader that only allows signed Firmware to load. This prevents users from booting Custom ROM images not signed by Motorola that have become popular in the Droid modding community." http://en.wikipedia.org/wiki/Motorola_Droid#Motorola_Milestone http://en.wikipedia.org/wiki/Motorola_Droid#Motorola_Milesto... Many Motorola phones are similarly restricted. Did I mention carriers are phenomenally stupid?