OK it's not called JVM, but Dalvik VM. Its role is the same : "read .apk/class" and interpreting it. Managing the garbage collector & memory. It's a level between OS/drivers and the application.
> overloading the heap with lots of String objects in a loop is a common > mistake - the GC often kicks in to avoid OutOfMemory errors), rather Agreed. There are a lot too many objects in memory ... > compiler called javac to compile the source files into bytecode > (again, Dalvik (Android) bytecode is different to Java bytecode). Yes : byte code in .class is different than in .apk Dalvik Byte Code is not the byte code used by the processor (which can be different depending on devices). Read/search documentation on .class byte code for an example. Do some Assembler or read how it works. You will understand what I mean :-) So : there is a conversion/interpretation somewhere... which requires times/RAM... Anyway : I think Java was the good language (many API/libraries, portable, a lot of people knows it). Google did the good choice. But again : don't expect app as fast as on other OS. -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
