MobileRead Forums - View Single Post

Marrko · 01-21-2012, 06:01 PM

Tales about IT 20 years ago are a bit off topic, don't you think so?

Coming back to the present state of affairs, you need to realise that ereader hardware architecture is underpowered in many ways because of two requirements - a) battery must last weeks, not hours; b) thickness and weight of the system must be very small. Which in turns means that the heat emission from mainboard must be almost null. Hence computational power is limited.

Last but not least, core function of reading (reading app at the high level and driving e-ink screen on the low level) is computationally very much resource consuming. Keep in mind that this function must deliver reasonably short wait times while redrawing pages, even if processor is operating only at 800 Mhz max.

01-21-2012, 06:01 PM	#15
Marrko Member Posts: 15 Karma: 10 Join Date: Jan 2012 Device: eSlick	Tales about IT 20 years ago are a bit off topic, don't you think so? Coming back to the present state of affairs, you need to realise that ereader hardware architecture is underpowered in many ways because of two requirements - a) battery must last weeks, not hours; b) thickness and weight of the system must be very small. Which in turns means that the heat emission from mainboard must be almost null. Hence computational power is limited. Last but not least, core function of reading (reading app at the high level and driving e-ink screen on the low level) is computationally very much resource consuming. Keep in mind that this function must deliver reasonably short wait times while redrawing pages, even if processor is operating only at 800 Mhz max. Last edited by Marrko; 01-22-2012 at 03:59 PM.