I am so fed up with JME, I really hope Android does kill it off. Sure, Android has its annoying problems too, but Google has done much better with Android than Sun and the JCP ever did with JME: it was inexcusably idiotic of them to let OEMs and other dissemblers gut the WORA dream with such a farce of specification and implementation.
What I am referring to is the nightmare of 'fragmentation' they allowed by allowing OEMs to call their devices compliant, when not even the HTTP connection APIs would work consistently: it is notorious that developers often had to forego using the HTTP APIs completely, relying on java.net.Socket just to get code that would work semi- consistently across different OEMs and even different models from the same OEM. And what a mess they made out of the Address Book API! Only Nokia did a half-decent job. Yet Sun let them get away with it. Yet mention of this in the trade press is sparing. Even http://www.comp.nus.edu.sg/~damithch/df/device-fragmentation.htm#Java_Vs_non-Java_applications, which in other respects is good at describing fragmentation, downplays this aspect quite drastically saying only mild things like, "carriers are exacerbating the fragmentation problem by imposing various restrictions to gain economic advantages." On Sep 17, 9:17 am, Frank Weiss <[email protected]> wrote: > Daring to go OT, I'm wondering if Android is the JME killer. As mentioned by > the previous poster, JME is not all that WORA (write once run anaywhere). > Aside from layout and some other issues, Android looks like it is the > closest yet. Thoughts? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
