3 ms·

What’s annoying is when you want to look back at something earlier in the book. Then you have to use the clunky search and hope you don’t lose your current plac

What’s annoying is when you want to look back at something earlier in the book. Then you have to use the clunky search and hope you don’t lose your current place.

tombert 6d ago
KOReader has bookmark support; if I need to go back a few pages (or use the search), I'll just set a bookmark for my current place so I can easily jump back.
- damontal 6d ago
  Right so now we need a workflow to do something as simple as looking back a few pages. I know it’s necessary but it’s definitely a regression.
  - TeMPOraL 6d ago
    The constraint here is the e-ink refresh rate. That constraint does not exist on regular screens, which is why I'm surprised neither mobile reader apps or even desktop software takes purposeful advantage of it: fast scrolling back with fine, per-page control, keeping page in-place and zero perceptible latency rendering full page. With a finger drag or click&drag movement, this can easily be even faster than with paper books. I know this works because I've seen it with some PDF readers on desktop in the past, when I lucked into a combination of lightweight document and right "fit page to display" scaling. And, of course, this works natively in browsers with PgUp/PgDown, but only on the few remaining websites that haven't been thoroughly shittified (no "en-" there on purpose) with JavaScript and excessive styling.
  - wiether 6d ago
    When you go back in a physical book, you also put a bookmark (either an actual bookmark or one of your finger) to be able to resume reading where you were, no?
  - tombert 6d ago
    To each their own, it has never really bothered me honestly.
dewey 5d ago
That's the only issue I have with ebooks and the reason why I would never read a technical / reference book on it where you want to jump around and have your fingers in some pages to flip back and forth.

3 ms·

What’s annoying is when you want to look back at something earlier in the book. Then you have to use the clunky search and hope you don’t lose your current plac

by damontal 6d ago

What’s annoying is when you want to look back at something earlier in the book. Then you have to use the clunky search and hope you don’t lose your current place.

tombert 6d ago
KOReader has bookmark support; if I need to go back a few pages (or use the search), I'll just set a bookmark for my current place so I can easily jump back.
- damontal 6d ago
  Right so now we need a workflow to do something as simple as looking back a few pages. I know it’s necessary but it’s definitely a regression.
  - TeMPOraL 6d ago
    The constraint here is the e-ink refresh rate. That constraint does not exist on regular screens, which is why I'm surprised neither mobile reader apps or even desktop software takes purposeful advantage of it: fast scrolling back with fine, per-page control, keeping page in-place and zero perceptible latency rendering full page. With a finger drag or click&drag movement, this can easily be even faster than with paper books. I know this works because I've seen it with some PDF readers on desktop in the past, when I lucked into a combination of lightweight document and right "fit page to display" scaling. And, of course, this works natively in browsers with PgUp/PgDown, but only on the few remaining websites that haven't been thoroughly shittified (no "en-" there on purpose) with JavaScript and excessive styling.
  - wiether 6d ago
    When you go back in a physical book, you also put a bookmark (either an actual bookmark or one of your finger) to be able to resume reading where you were, no?
  - tombert 6d ago
    To each their own, it has never really bothered me honestly.
dewey 5d ago
That's the only issue I have with ebooks and the reason why I would never read a technical / reference book on it where you want to jump around and have your fingers in some pages to flip back and forth.