Re:This is what happens when you let Java people write apps ...
by bad_user on Friday April 09, 2010 @07:13PM
(#1254144)
First of all "amazing" is subjective, and all current mainstream tools are amazing in some way.
Android has Dalvik, which is a register-based virtual machine (as compared to the stack-based JVM) that's optimized for solid-state memory (which has slower access times) and with bytecode optimized for interpreting on ARM processors. I's questionable if it was the right thing to do, but it's still amazing.
Having a VM on a mobile device is debatable, but it's higher level and that's one way to achieve portability and to reduce accidental errors (memory leaks, buffer overflows).
And what language would you propose they should use? Their own? C#? And keep in mind that it has to be a language that doesn't need lots of magic to make it run efficiently, like a tracing JIT (a pragmatic choice based on current real-world constraints).
Your analogy to cars doesn't hold water. You can't build an F1 without proper knowledge, and all the tools in the world won't help you with that.
Android has Dalvik, which is a register-based virtual machine (as compared to the stack-based JVM) that's optimized for solid-state memory (which has slower access times) and with bytecode optimized for interpreting on ARM processors. I's questionable if it was the right thing to do, but it's still amazing.
Having a VM on a mobile device is debatable, but it's higher level and that's one way to achieve portability and to reduce accidental errors (memory leaks, buffer overflows).
And what language would you propose they should use? Their own? C#? And keep in mind that it has to be a language that doesn't need lots of magic to make it run efficiently, like a tracing JIT (a pragmatic choice based on current real-world constraints).
Your analogy to cars doesn't hold water. You can't build an F1 without proper knowledge, and all the tools in the world won't help you with that.