3 ms·
300ms is on a low-end android phone, which is nice, but I wonder what's the performance impact on something more modern, like a 2 year-old iPhone.
by e63f67dd-065b 3y ago
300ms is on a low-end android phone, which is nice, but I wonder what's the performance impact on something more modern, like a 2 year-old iPhone.
- silvestrov 3y agoOn high end phones it is more of a "battery impact" than a "delay impact".
- dredmorbius 3y agoI've been using an e-ink device extensively for the past few years. It's nominally an e-book reader, though in truth it's an Android tablet with an e-ink display. I use it for both reading books and websites. I'd recently looked at battery usage and found that my preferred browser (Einkbro) uses ten times as much battery per hour of reading than Neoreader (the Onyx BOOX stock ebook reader). Einkbro is a solo-developer effort (based on the FOSS browser), so I'm not sure how much energy-usage optimisation it has or is lacking. It's sufficiently pleasant to use (relative to other Android browser options) that I don't use other browsers significantly ("Neobrowser", a re-branded Chromium, and Firefox Fennec are both installed, and used occasionally). But it really sucks down juice. That's on top of the fact that many web pages are larger (storage, memory use) than a full-length book. Typical e-pubs run ~500 kB -- 5 MB, with graphics-heavy or scanned-in books running up to 100+ MB. I also find that reading pre-formatted, laid-out content with pagination and navigation is increasingly far more pleasant than scrolling through a Web document. HTML as presently instantiated has some pretty sharp corners and limitations.