|
It's not a matter if Java is slower than compiled C code. It is, it always will be. It's a matter if the Java is fast enough to run an ereader. Guess what, it is. The Android OS is designed to be used for phones, and telephony requires real time fault tolerant buzzword buzzword. It requires something that works really really well, and google chose Java for that.
The slowness we are seeing in the nook is not because of Java itself but the way in which Java was used. Bugs, poor code are the culprit of the "slowness" of the nook.
But that's all mute in my opinion. The touch screen has been fast enough for me when I used it and the real bottleneck will always be the eInk screen. It is the slowest part of the nook, or any ereader that uses the same model as the nook does.
|