News for hackers. Stuff that matters.

A comment on First set of Android apps for ChromeOS. Parent comment

Re:First set of Android apps for ChromeOS by cwyers on Thursday September 11, 2014 @03:58PM (#8304790)
Right now this is a very Parallels sort of solution, where you run the app in a VM. No actual merging of anything is going on, there's just a runtime that lets you run Android apps on ChromeOS, looking like they do on Android.
[ Parent | on HN ]
Re:First set of Android apps for ChromeOS by ucsdrake on Thursday September 11, 2014 @04:09PM (#8304850)
I think it's likely that they're writing a runtime for dalvik to run on chromeOS, which, is essentially 'merging' though now you're just arguing semantics.
[ Parent | on HN ]
Re:First set of Android apps for ChromeOS by fluidcruft on Thursday September 11, 2014 @05:27PM (#8305251)
(Dalvik is dead. You probably mean ART.)
[ Parent | on HN ]
Re:First set of Android apps for ChromeOS by jmgrosen on Thursday September 11, 2014 @05:58PM (#8305409)
Dalvik the runtime is dead. Dalvik the bytecode is not.
[ Parent | on HN ]
Re:First set of Android apps for ChromeOS by snlacks on Thursday September 11, 2014 @06:28PM (#8305556)
Aren't Android apps run in a virtual machine (because of the Java roots) anyway?

(Genuine question, not me being a smarty pants.)

[ Parent | on HN ]
Re:First set of Android apps for ChromeOS by ahomescu1 on Saturday September 13, 2014 @03:24AM (#8311816)
"Virtual Machine" is an overloaded term. It can either mean virtualization of an existing CPU (like the x86), or of an abstract bytecode machine (like the JVM or Dalvik). In the former case, you have to efficiently virtualize/emulate an entire system (including stuff like hardware devices and CPU interrupts); in the latter, you only have to execute the bytecode program well, which most VMs of this sort compile just-in-time (they compile the bytecode program into a native equivalent at execution time).
[ Parent | on HN ]