Re: Oracle sues Google over Java patent infringement in Android
 

This is all I can think of when Larry Ellison is mentioned:

http://www.salon.com/21st/books/1997...v_18books.html
http://www.salon.com/21st/books/1997..._18books2.html

Re: Oracle sues Google over Java patent infringement in Android
 

I can also attest to personally being awoken at night sometimes whenever Ellison would take off in his private jet at night at full speed against FAA rules back when I lived in Santa Clara, RIGHT next to the San Jose Intl Airport. To us locals, he's gotten a reputation for being kind of an inconsiderate jerk to people in general in addition to his professional miscreant behavior.

Re: Oracle sues Google over Java patent infringement in Android
 

This is somehow mentioned in his wikipedia page. However, it would be nice if you put the above wording there too.

Re: Oracle sues Google over Java patent infringement in Android
 

Hah! A wikipedia mention of it. That's funny. :) I just lived it, didn't know it was a "thing" to be posted anywhere.

I seem to remember it had more to do with noise levels taking off at night--the article says it was a weight issue that he was violating. I used to live VERY close to the airport, heard and saw someone's jet (looked like a Lear to me at the time) and I used to know people that talked to each other placing the blame on Ellison, and it was believable given the way he carried himself. Can't say I'd want to post it on Wikipedia as if it was something I could cite with relevant articles or pictures (wish I had taken some), but I can at least attest to a repeated incident that people kept telling me were Ellison. I personally believe, to this day, that it was probably him.

Edit: Also, just to make it clear, it didn't bother me so much. I tended to be a night owl and up all night most of the time anyway, but it did wake me up a few rare times. More amusing than annoying in my case, but I remember locals not feeling so amicable. :) But, I guess I did find some relevant articles that might agree with what I remember:

http://www.nonoise.org/news/2000/mar...onal%20Airport
http://airportnoiselaw.org/news/june-23.html

I wish I could search the San Jose Mercury News for it, but they don't go as far back as the years I'd lived there. Aw well.

Re: Oracle sues Google over Java patent infringement in Android
 

From what I'm reading, the details appear to show that there are eight claims, seven on patents, one for copyright infringement. Like I'd said at the start, I got the impression this was more about patents than copyright--my first impression seems to be right, so far.

There's an EXCELLENT study/breakdown of what this is about here on Groklaw:
http://www.groklaw.net/article.php?s...00815110101756

Re: Oracle sues Google over Java patent infringement in Android
 

Also, to bolster another point I thought I had right earlier (and apparently did), under the section where it says, "Charles Nutter, explains about what Google did and why he thinks it did it and what might result:"

So yeah, as a technical clarification, it doesn't run Java tokenized code--it recognizes Java LANGUAGE that you type in, but it generates DALVIK (Android) bytecode.

Re: Oracle sues Google over Java patent infringement in Android
 

Nobody suggested that it did.

The only suggestion has been that Google need to convert from Java bytecode to Dalvik bytecode, thereby implying that Google don't ship a Java language compiler which is capable of generating Dalvik bytecode directly. Rather, they ship a Java language compiler that generates Java bytecode which is then converted into Dalvik bytecode.

I wonder where Google obtained the Java language compiler and tools they're using?

Re: Oracle sues Google over Java patent infringement in Android
 

I don't see that anywhere in the suit. In fact, they seem suspiciously ambiguous about their copyright claims (very SCO-like, in fact) and they didn't list anything specific. According to another part of the article I'm reading so far...

Since that isn't a Google citation, I can't rely on it as a fact, mind you--but if it's accurate (and much of the rest of the other citations and articles they list would seem to concur with this), then it wouldn't make sense for the ADK to produce Java bytecode. (Why compile to tokenized code just to covert to another tokenized code, seems an incredibly weird way for a compiler and development kit to work--and also goes against the explanation that you need to recompile your code into Dalvik binaries.) Still, nothing in here that goes against that particular claim so far--it's just not something that seems likely to me and it's just not something anybody's mentioned, even in the claims.

Re: Oracle sues Google over Java patent infringement in Android
 

Also... I am sooooo totally not a lawyer. :) I'm just interested in reading up on this and trying to understand it. :)

Re: Oracle sues Google over Java patent infringement in Android
 

IANAL but I'd say it's the following copyright claim:

It seems to be saying that Google are inducing end users and device manufacturers to use copyrighted Oracle technology without an appropriate licence, ie. Java compilers, tools and documentation.

Possibly two reasons:

1) Google need to convert existing classes from Java bytecode to Dalvik bytecode in order to simplify porting of existing Java apps and classes, hence the existence of the dx tool which takes a Java bytecode class and spits out a Dalvik bytecode class

2) Given the existence of dx, why go to the lengths of creating your own Java/Dalvik language compiler - just use an existing Java language compiler and bolt the dx tool on at the end to convert the newly generated Java bytecode into Dalvik bytecode. No need to reinvent the wheel.

Which is a fairly ambiguous statement, to be honest. "Recompile" could describe precisely the function performed by the dx tool.

Unless anyone can state categorically that Google have their own clean-room Java language compiler which spits out Dalvik bytecode without generating intermediary Java bytecode I think Google may be on a slightly sticky wicket.

So far I've only seen evidence that confirms the intermediary bytecode approach.