Well as we are diverting from the topic of this thread, I make my final rant
You are correct, it is good on paper and in real life applications; several billion of them.
I can't share your enthusiasm. As I see it, Java's main downside, besides interpreted code and VM architecture, is the worldwide availability of lousy coders.
I'm sorry, your hardware sucks... the warm up has nothing to do with the code. The Java inside is executed in under one millisecond. The manufacture's poor understanding of HIG is the cause of your frustration.
We can argue that hardware is cheap and fast coding is the way to go, but this does not excuse for huge compromises done for the sake of platform independence and "cost-effective" software development.
And I can assure you, the hardware inside the 12-year old device does not even compare to the new, Java-based ones performance-wise. Still, the UX excels.
I know, life is too short to code in assembler, but I'd take tight & efficient machine-optimized code any day over platform-agnostic P-code.
The bottom line : we've traded the efficiency of executable machine
code for the efficiency of software manufacturing
process.