I agree with FrustratedReader in everything, except for
Quote:
Originally Posted by FrustratedReader
1) The VM for the Apps, which are essentially really Java.
|
The apps are built in java. The frameworks used by android are plain C++. the Dalvik/ART machines are very well optimized and comparation with JVM has no sense.
Given that plain "c/c++/whatever fast compiled language" apps run inside the VM using the NativeActivity framework and invokation of native methods is done with JNI, which adds some overhead, there's usually no gain in building "c/c++" apps for android.
Which makes android really bad for single use devices is the kind of services that run everywhere and are intended to abstract certain things for easy development and the constraints Google makes.
Can be workarounded?: yeah. BarnesAndNobles and Rakuten/Tolinos seem to do a good job creating a AOSP based os that's not bloated.
In the end if you start by debloating android you'll end with a plain linux distribution. That and talk to the linux framebuffer directly makes sense for an e-ink reader app. But using the android view hierarchy, with its WindowManager, its SurfaceFlinger and dadada adds little overhead to that.