I'm not so sure.

A "JVM" is not a Java language interpreter anyway but a Java byte code interpreter. AFAIK all those other languages only run on Dalvik by first being compiled to Java byte code format, thus it is arguable that they are all "Java" as far as the VM goes.

What Google needs is something that compiles directly to Dalvik's own native format which has no "Java" at all in the pipeline.

> AFAIK all those other languages only run on Dalvik by first being compiled to Java byte code format

You seem to think the JVM bytecode format is specific to the Java Programming Language™; why is this?

Admittedly Sun has muddled things up here by using the word "Java" to mean many separate things.

wtf? You apparently don't know much about the JVM because AFAIK it was the first VM people started targeting other languages at.

Anyone care to explain the downvotes? The poster I replied to claimed that Dalvik is different because people target different languages at it. Not only do people do this for the JVM, I think it was probably the first VM where people did this.

Easy: read the first 7 words of your post.

The UCSD P-system was a VM that ran several languages, and was at least a decade older than the JVM.

Ok, so that makes my "AFAIK" statement incorrect, but that doesn't affect the point nor explain the down votes.

things that will get you downvoted include statements like "wtf, you apparently don't know..."

1) impolite. 2) your comments should concentrate on what you can add to the convo, not what others haven't.

I mean, it also doesn't help that your statement was incorrect (P-system as mentioned), but being rude in what is ideally a civil forum dedicated to a stated purpose is not helpful.

> The poster I replied to claimed that Dalvik is different because people target different languages at it

Reading comprehension, bro. Give it a try.

The Dalvik VM, like the Java Virtual Machine, is quite capable of running languages that aren't Java. There's nothing controversial or incorrect about that statement.