Featured post
design - why android is built on a VM (Dalvik) -
i curious know made google choose develop android's framework on java vm.
in process of writing code android 6 months now, observed running code on vm in resource limited platform slow. there lot of overhead involved. know java portable etc etc, not possible @ use native languages , both performance , features offered vm ? performance oriented applications 1 still ends writing native code , wrap jni,
so why did google choose particular stack :
- arm based core (understandable, arm best mobile devices)
- linux (open source)
- java vm (my question)
edit : know java - jvm run's on par c++ applications on server, not on android. respect android not case - matter of experience, c++ code wrapped jni runs far faster java code (note have checked exact same code static block in java) agree answer on other platform.
the dalvik vm uses own bytecode, not java bytecode. it's designed fast (relatively speaking). think "vm" part of title bit of red herring, people tend assume "slow" no matter what. said yourself, you're working "resource-limited platform" -- that's main cause of slow performance, more dalvik vm.
disclaimer: not expert on dalvik or android in way, shape, or form. however, seems people can tend make lot of assumptions android based on ideas "it uses vm" , "you write applications in java", without looking platform further that.
see this video more information ever wanted know on dalvik vm internals (from google i/o 2008).
- Get link
- X
- Other Apps
Comments
Post a Comment