Linked by Eugenia Loli on Tue 7th Feb 2006 01:02 UTC
Permalink for comment 93568
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
More News »
Sponsored Links



Member since:
2005-12-31
I'm not sure splintering the mobile world further with Yet Another API is really a good idea. There's nothing inherent in J2ME that says apps must be ugly and slow - my own phone runs them at native speeds directly on the chip (no JIT compiler or interpreter to slow things down), and the LCD widget toolkit J2ME provides is already interfaced to the native toolkit meaning that Java apps look and feel almost native on these phones. There's no reason a phone manufacturer can't go the whole way and add API extensions to allow Java apps to access native facilities when available either.
J2ME is, for better or worse, pretty much a standard. It's better IMHO to work with it than use the native Motorola APIs just because it's Linux.