On Tue, 11 Apr 2017 08:29:07 -0300 Solerman Kaplon <soler...@gmail.com> said:
> Em 11/04/2017 06:52, Carsten Haitzler (The Rasterman) escreveu: > > > > then why does android precompile java apps to native code on installation > > now as opposed to just keep interpreting? :) > > > > Because java is jitted and doing JIT takes time, memory and battery to do. the original point was "interpreting bytecode is good enough". this is what java did in the 1.x days... then it gained a jit for more speed... this is what android did too. it interpreted java bytecode with davlik then eventually now moved all the way to compiling into native on install. in interpreting the bytecode was good enough why did anyone bother to do all this work getting the code to run as fast as possible with jit's and full compilation to native instead of just interpreting? :) > Plus, on usual VMs, there is no caching of JIT code. So they just do the JIT > once and save it for later reuse (Its more complicated than JIT cache, but > you get the point) yeah. i know why precompile vs jit. but i'm asking then why do any of this if bytecode interperting is fast enough for all apps? :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
