This post originated from an RSS feed registered with Java Buzz
by Fred Grott.
Original Post: Android's Java Flaws
Feed Title: ShareMe Technologies LLC-The Mobile Future
Feed URL: http://www.jroller.com/shareme/feed/entries/rss
Feed Description: A Weblog about Java programming and digital convergence on mobile devices in such areas as P2P and collaborative technology.
Before I get into this, coming up with a new language such is Java is very hard and is comparable in difficulty to mobile handset hardware design. Thus, this not a blame piece towards Google, OHA, OHA members, Sun Microsystems, or apple, or even Steve Jobs. My thesis is that both Apple with Steve Jobs and the iPhone and Google with OHA have valid points about doing mobile a different way and those both points can mixed into new approaches with Android's Java.
Java has a flaw. I have talked about this flaw before in my Arrays vs Collections piece which was dugg by zone users before, Arrays vs Collections. Suffice it to say if you avoid collections you speed up java. Yes, that is an oversimplification, Google Javolution for the science papers and actually read them.
e
When Steve Jobs stated that Java would not be on iPhone he was not just referring to the bad Java JVM design for mobile use such as stack vs register JVMs but also he was talking about certain flaws in the java language itself. The speed difference of using Arrays vs Collections is somewhat mor eof symptom than the full problem.
One of the reasons why Google and the OHA implemented a XML structure to the UI and hooks for that for developers is that that is one of the strategies of speeding up Java via the Javolution research as currently the Javolution recommendations in changes in the Java language are slowly being handled by the JCP via the RTS java specification.
With both Google and OHA implementing some XMl we do not have to fully use all of the Javolution library techniques to speed up our Android native java applications. By implementing just a few techniques we can get the speed that is often required for gaming and etc.
My bias disclaimer is that I am using Javolution libraries in my implementation of the event. eventManger, que, and polling classes that grab OS and user event sot make them accessible to the embedded webkit webview to do Android Mobile Web applications that are integrated with OS and user events.In interest of full disclosure there is a GPL'ed library that adopts a different approach that does not address Java short-comings in their eventManger and Polling classes.
Now, Steve Jobs could you get a unit testing framework on the iPhone devices? Please..
Previous Topic
