3 ms·
Thanks, that's interesting! It seems reasonable—if Google was explicitly trying to enable compatibility, that should be allowed, whereas if they were just tryin
by Wowfunhappy 6y ago
Thanks, that's interesting! It seems reasonable—if Google was explicitly trying to enable compatibility, that should be allowed, whereas if they were just trying to save a buck, that should be illegal.
Of course, in reality Google's decision was probably a little of both, right? They selected a technology based on a wide range of factors, including development costs and compatibility.
I'm still concerned that a decision in Oracle's favor would have a massive chilling effect on everyone else. All companies want to limit their potential liabilities. How can you prove in advance that you selected a language or API for the sake of compatibility, even when that is in fact the driving factor?
- dlubarov 6y ago> Of course, in reality Google's decision was probably a little of both, right? I wouldn't think that Google's development costs were part of the decision. There aren't that many Java APIs -- as the article says, it's ~11k lines of definitions -- so Oracle is seeking ~$818k per line. Assuming Google's lawyers predicted that there was some risk of a lawsuit like this, any engineering costs associated with redesigning the APIs would just be negligible compared to the legal risk. One could argue that it is quite difficult to design a good API, but Java's APIs are frankly full of mistakes: Date/Calendar, immutable collections with no type safety, "optional" methods like Iterator.remove, etc. It wouldn't take a team of world-class engineers to come up with something better with the benefit of hindsight. On the other hand, developer familiarity and compatibility with existing Java libraries could have had a significant impact on Android's adoption. I think that was what justified the legal risks.
- fomine3 6y agoMany libraries comes from Java world are able to use by copying API. So saved lines is not just ~11k.
- pjmlp 6y ago"Android chief Andy Rubin said java.lang APIs are copyrighted in 2006 email" https://www.cnet.com/news/android-chief-andy-rubin-said-java-lang-apis-are-copyrighted-in-2006-email/ https://www.cnet.com/news/android-chief-andy-rubin-said-java... "Copyright and consequences: Google’s Andy Rubin defends Android to jury" https://arstechnica.com/tech-policy/2016/05/copyright-and-consequences-googles-andy-rubin-defends-android-to-jury/ https://arstechnica.com/tech-policy/2016/05/copyright-and-co... > "We've been over a bunch of these, and we think they all suck," Lindholm wrote. "We conclude that we need to negotiate a license for java under the terms we need."