The small device platform for Java (the various flavors of MIDP, etc)
was always a highly structured and fragmented mess. The same classes
had the possibility of different byte code implementations depending on
the capabilities of the physical platform, not to mention the various
small real-time and Java-on-a-chip engines that were popping up.
Android has helped unify that, a kind of tough love for Java as a whole
(though I doubt they care much about Oracle). It has its own
versioning problems, those are slowly being resolved. Android is not
trying to fork the JDK, in my view (which would indeed be
suit-worthy). If this forces Oracle to clean the small device house,
(by losing the suit in a graceful way), Java will be better off.
Carl
On 8/23/10 7:29 PM, Russ Abbott wrote:
Good article. Makes the case that Oracle's suit against Google
parallels Sun's suit against Microsoft a decade ago when Microsoft
wanted to implement a Window-only version of Java.
-- Russ
On Mon, Aug 23, 2010 at 9:06 AM, Owen Densmore
<[hidden email]>
wrote:
Slashdot pointed out this article:
http://www.infoworld.com/print/134392
.. which makes a good case for Oracle.
I found it surprising, but the argument does make a good case for
Oracle strengthening the Java platform, maintaining its coherence.
Dalvik would not run java byte codes, for example .. requiring
recompiling Java source to the .dex format.
I think I agree, but I haven't had my coffee yet!
The usual incoherent /. babble is here:
http://developers.slashdot.org/story/10/08/22/1534205/
-- Owen
============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
lectures, archives, unsubscribe, maps at http://www.friam.org
============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
lectures, archives, unsubscribe, maps at
http://www.friam.org
Locked
Aug 23, 2010; 4:06pm
