That's partially true; webOS 3.0 has no Java as far as I'm aware, deferring to node.js for its services instead. webOS prior to that (e.g., Mojo era) contains an absolute trove of Java all over the damned place. I remember dissecting the media system looking for private APIs in parallel with developing a webOS application and many points led right back to Java-based services that assisted in doing a lot of perfunctory tasks.
In fact, I distinctly remember asking the Palm webOS developers when I discovered in their Java-based media services a particular call that instantly parsed SHOUTcast/Icecast-style playlists of many various formats with ease whether it'd become a public API call. It never did.
If HP races to finally reconcile the two sides as a promised a half-year ago a la Android's ICS, then there might be no obstacles to the Java argument. Until then, however...
In fact, I distinctly remember asking the Palm webOS developers when I discovered in their Java-based media services a particular call that instantly parsed SHOUTcast/Icecast-style playlists of many various formats with ease whether it'd become a public API call. It never did.
If HP races to finally reconcile the two sides as a promised a half-year ago a la Android's ICS, then there might be no obstacles to the Java argument. Until then, however...