3 ms·

more and more companies are stripping their desktop framewoks for native code on mobile. Mozilla ditched XUL for native in mobile ff a while back because of per

• RyanZAG 14y ago
  Android doesn't really have that many layers. It often comes off more complex than it really is, mostly from pretty good design work on the Android designers side. Calculations: CPU - Dalvik VM doing JIT into ARM ASM Graphics: GPU - OpenGL/Drivers -- (a) Directly running OpenGL calls (native) -- (b) Dalvik VM doing JIT --- Semi-lightweight translation of 2D drawings You don't really lose more than a couple percent on the 'many layers' compared to writing raw assembler, aside from using Android's View framework which is about as performant as most GUI toolkits in most situations.
• krschultz 14y ago
  I think the Facebook article throws around the word "native" a little liberally. It sounds like they are doing bitmap processing in the true "native" sense (i.e. C). The earlier references to "native" make me think they are referring to standard Android/Java code as opposed to WebViews.