Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> This fragments the ecosystem and essentially allows Android to benefit from the works of the Java rightholders without making those contributions equally as useful to Oracle Java itself.

Java SE, Java EE and JavaME are incompatible. Java was already fragmented by their creators



> Java SE, Java EE and JavaME are incompatible.

Hell, JavaME wasn't compatible with JavaME, depending on which vendor versions you were comparing. Sony Ericsson had classes totally different from Samsung or Nokia. Add CLDC versions and varying CPU and memory capabilities to that toxic hellstew to effectively kill the WORA dream.

Sun/Oracle can't blame Google for their abysmal mobile strategy.


I can attest to this, and wrote a validation package to detect the differences among Java ME implementations back when I was doing mobile search apps for Java ME devices. A particularly annoying irony is that if you tried to use the supposedly standard ME UI classes, that's where most of the poorly spec'ed behavior lived, which is what all those vendors pointed to to justify doing their own UI classes. Never mind the intentionally loose specs for things like threading behavior.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: