View Single Post
Old 02-12-2022, 04:45 AM   #48
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 79,964
Karma: 147448039
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by AnotherWanderer View Post
You've stated that the browser on readers don't work a fair few times now. What are you judging this by? From pictures of even old Kindles I can only assume that they have fairly decent CSS and JavaScript support, although I imagine JavaScript heavy pages or pages with complicated stylesheets would get painful to use quite quickly.

I put "usable" at reading plaintext, rendering an HTML form and submitting it. If any reader failed to render 68k.news I would be amazed (and somewhat disappointed, I have a very cheap PRS-T1 on it's way as an experiment for using an eink device as a news reader).
The T1 um....No. Do you know that the T1 is slow and low resolution and it can freeze, lock up, or be really slow when reading eBooks with high-res graphics such as the cover and title page? Do you really want that?
JSWolf is offline   Reply With Quote