Believe that all of us working in video games want program execution on mobile devices to be as fast as possible. My brand-new desktop PC is not fast enough for what I want to do, so an Android phone running a bytecode interpreter is that much further.
I also don't think you know what "vaporware" means. If it is actually running on physical hardware it's not vaporware; it is just not in consumer hands yet. (Since Engadget has played with it on a physical phone... it is known to be real.)
Minor point, but technically a JIT compiler doesn't replace an interpreter. The latter is still there (written in assembly nowadays), and the VM has to trace hotspots and balance the cost of run time compiling vs. the cost of normal interpretation. Of course a JIT code cache helps to avoid the compilation overhead.
To be even more nitpicky about it, a JIT compiler can replace an interpreter. There are compile-only JIT's, like Jikes RVM. But good point in this case, especially since Dalvik is a tracing JIT and relies on the interpreter more than a method JIT usually would.
Believe that all of us working in video games want program execution on mobile devices to be as fast as possible. My brand-new desktop PC is not fast enough for what I want to do, so an Android phone running a bytecode interpreter is that much further.
I also don't think you know what "vaporware" means. If it is actually running on physical hardware it's not vaporware; it is just not in consumer hands yet. (Since Engadget has played with it on a physical phone... it is known to be real.)