Oracle sucks soooo bad. Must need some revenue. Seems like all their licensing income would be enough...guess not.
Doesn't sound like they are getting licensing income from Google.
Oracle sucks soooo bad. Must need some revenue. Seems like all their licensing income would be enough...guess not.
It's late here - but none of that makes any sense. Android is NOT Java. So there is no question of a JVM and fragmentation. It uses standard Java language features even if their implementation underneath is not a standard JVM. If they had licensed a JVM they would end up with J2ME - no one bought that crap. (Or desktop java for that matter.)
Not sure how that makes Google bad - they just wanted flexibility for their platform without Sun dictating. Sounds right to me.
Google cannot co-opt Sun/Oracle's control of its IP and patents through attempted splintering of standards (or other potentially anticompetitive tactics), no matter how important they think they are. Flexibility for your platform is not your right when you're using someone else's creation. If Google wanted complete flexibility without being encumbered by potential IP problems, they should've paid the rightful owner of the technology or developed their own language and interpreter package from scratch (without violating patents, naturally). It would appear they didn't do that, because they assumed they were too large and frightening for anyone to call them out.
Is J2ME terrible? Most certainly; it is universally derided. But being big, or potentially 'innovative', doesn't make you above the law. Sane people don't steal.
Please educate yourself. Google would end up with crap if they licensed Java - it would imply implementing standard JVM for Android - with all the bloat and generic J2ME crap. At the rate they are innovating if they licensed a JVM it would take them decades to get it through JCP. No sane person would ever do that.
They can claim anything they want, if they're found to have violated Oracle's patents their claim of writing Dalvik from scratch won't matter. The effect is the same, they're trying to co-opt Oracle's ownership of IP relating to Java by marginalizing their mobile product and not paying for it.Google wrote Dalvik VM themselves from scratch. They do not claim Android is Java compatible.
No, but they're obligated to follow the rules.They are not obligated to use their own language.
Infringing on patents isn't stealing?There is no stealing involved here. Only patents.
Google wrote Dalvik VM themselves from scratch. They do not claim Android is Java compatible. They are not obligated to use their own language. The standard part - language features are supported as-is on the Dalvik VM - they did not invent their own extensions to the language.
There is no stealing involved here. Only patents.
Google has several options:
- License Java as a distributor and agree that Oracle controls the future direction Java.
- Prove their implementation is not Java, and therefore they are not in infringement.
- Abandon the current version of Android, and reimplement it another manner.
No, but they're obligated to follow the rules.
Infringing on patents isn't stealing?
Google does not claim Android is Java - by choice. So this is not the same as Microsoft fragmenting Java. They just use the standard Java 5 language features as-is to the point that Sun javac can compile it. After that though it's anything but Java.
Ah, okay. Yeah, I don't believe Google can be accused of that. I still think trying to take control of IP from Oracle by brute force is theft, though.I meant they are not "stealing" JVM code from Sun/Oracle (unlike what SCO et. al. claimed vs. IBM for e.g.)
That's a matter of opinion, Oracle (and quite a few other people) seem to think otherwise .- about patents who knows, most software patents are full of crap and prior art.
Do you work for Google? You sound like a lobbyist repeating the corporate line.
Yes Google doesn't claim to be Java compatible - a choice driven by an attempt to find a loophole that will let them clone what they want and fork the standard, much to the chagrin of the creators of the standard.
It is pretty clear they are trying to back door there way around the standard to run roughshod over the license holder and taking what they want and forge their own standard based on Suns Java work.
It's late here - but none of that makes any sense. Android is NOT Java. So there is no question of a JVM and fragmentation. It uses standard Java language features even if their implementation underneath is not a standard JVM. If they had licensed a JVM they would end up with J2ME - no one bought that crap. (Or desktop java for that matter.)
Not sure how that makes Google bad - they just wanted flexibility for their platform without Sun dictating and controlling (JCP). Sounds right to me.
Ah, okay. Yeah, I don't believe Google can be accused of that. I still think trying to take control of IP from Oracle by brute force is theft, though.
That's a matter of opinion, Oracle (and quite a few other people) seem to think otherwise .
I sound like a lobbyist to you because you have no understanding of the matter.
What standard are they forking? Do you even understand how Android makes use of Java? They use standard Java language features to the point where it compiles using Sun compiler.
What back door? They wrote their own software that takes standard Java class files, turn it into something that then runs on their own implementation of the Dalvik VM.
.
QFT. Any action Larry Ellison takes is to benefit Oracle. Period. Larry and Oracle bought Sun because they saw a value in the deal, no more and no less.Larry Ellison only cares for himself.
It's late here too
No, android is not Java, but does "support" Java. Of course they said they don't, explicitly, in order to avoid the scorn of Oracle, but I would call Harmony Java, and not its own, separate entity. Harmony is basically the same libraries, as you said, only its an Apache license with limited use, something that has to be looked at. While yes, they avoided a JVM by making their own (and their own bytecode), and while yes, it technically doesn't fragment the community since you cant run vanilla java due to minor library changes, it does, in fact, pose a fragmenting pattern in the community, just like MS did back then. You created a new java-like system, that's very similar in implementation, and even more similar library-wise; how does that not fragment the community? Now they have to code either for 1) Android or 2) Java, and furthermore, debug is now not a unified process. If android's implementation was exponentially different, then maybe, but since it uses Harmony it's close enough to create future fragmentations by picking one over the other.
As for the licensing; I'm not quite sure who got what in the end for MS's case, but I'm sure Google could have secured a nice deal for an agreement similar to Apple or MS. I understand the flexibility and hooks and what not, but what makes it bad is that in doing so they broke IP and possibly created future fragmentation for Java.
You sound like a lobbyist/lawer because you think as long as you find a loophole to subvert licensing it is perfectly OK, to do so.
Think about what you are describing.
Compile Java with Sun compiler to sun class files, run on JVM on mobile, you must license this.
Google ads another layer to convert that Sun Class file to their own new bytecode and now you can escape licensing. This is just a slimy loophole.
If I was sitting on a Jury for this, it is pretty transparent that Google is just looking to exploit a loophole to avoid licensing.
LOL! You have radical views of what constitutes as a slimy loophole.
What do you call it? It certainly wasn't the intention that you could get around JVM licensing by taking compiled Java code and simply converting it to a different bytecode.