|
Authored by: Ed L. on Saturday, April 21 2012 @ 08:19 PM EDT |
AFAIK -- not being a Java programmer -- JVM and Dalvik are two very different
beasts. My understanding is that all Java(tm) programs running on a system run
on the same JVM, whereas each Java(android) program is run by its own dedicated
Dalvik. Scheduling and IPC amongst the myriad Dalviks is handled by the
underlying Linux kernel, whose properties cannot be assumed by a generic
JVM.
Heck -- a generic JVM can't even assume its being run on Linux at all,
poor thing.
Which is to say that JVM must handle scheduling and IPC the same
amongst its client Java(tm) programs regardless of the underlying OS: Windows h8
same as Vista same as XP same as Linux 2.6.w same as Linux 3.x.y same as
z.system.foo.bar same as Solaris. Which is a pretty tall order. With Android
otoh, Google controls the entire stack. Each Dalvik can be relatively simple
because many of the traditionally more onerous JVM duties have been relegated to
the kernel where they belong.
:-)
--- Real Programmers mangle
their own memory. [ Reply to This | Parent | # ]
|
|
|
|
|