@b0rndead EXACTLY MAN! They buy up a crap load of other companies, I dont see why they dont partner up with these guys and work this into the actually OS. Happier users and that closer to shutting up Iphone fanboys who dont know how to shut up about their damn phone lol.
@Beatnik As several others have pointed out Google is already building a JIT for android. It's in the 2.0 and up sources but isn't enabled by default because it's still under heavy development and not yet ready.
Google's developers have rightly pointed out a JIT isn't high on their priority list for a few reasons: -the native development kit allows for speed in performance critical sections of apps -JITs require more memory which means less multitasking -mobile devices have limited resources so compiling and then executing code can be inefficient. On your desktop it doesn't matter as you have thousands of CPU cycles to spare but embedded is a whole other story -there are a lot of other areas of android that need more work and their development team is limited
Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
srsly?
cmon google! buy it and bake it into your next release!
@b0rndead EXACTLY MAN! They buy up a crap load of other companies, I dont see why they dont partner up with these guys and work this into the actually OS. Happier users and that closer to shutting up Iphone fanboys who dont know how to shut up about their damn phone lol.
@b0rndead
Agreed.
@b0rndead
Agreed, Google Please buy that Dalvik Turbo like for =====>YESTERDAY
@Beatnik As several others have pointed out Google is already building a JIT for android. It's in the 2.0 and up sources but isn't enabled by default because it's still under heavy development and not yet ready.
Google's developers have rightly pointed out a JIT isn't high on their priority list for a few reasons:
-the native development kit allows for speed in performance critical sections of apps
-JITs require more memory which means less multitasking
-mobile devices have limited resources so compiling and then executing code can be inefficient. On your desktop it doesn't matter as you have thousands of CPU cycles to spare but embedded is a whole other story
-there are a lot of other areas of android that need more work and their development team is limited
@b0rndead That would be nice, but the way it's being marketed makes me think it's likely to be proprietary, and not able to be merged back in.