News for hackers. Stuff that matters.
Re:Why books don't work (2019) by liability on Tuesday September 22, 2020 @01:23PM (#24557304)
> Reading a book takes more effort than it used to.

I agree with most of your points but not this one. The proliferation of audio books and text-to-speech (TTS) has made reading books easier than ever. Particularly TTS in my case; I can read an eBook visually for a few hours, then switch to TTS for a while to give my eyes a break, and in this way easily marathon books. Once you are accustomed to TTS you can turn the speed up very fast. I tune the speed on the fly to compensate for mental fatigue to maintain a consistent level of comprehension; when I'm 'in the groove' I can comfortably set TTS to around 750wpm. I can read visually faster than that, but only in a 'sprint', not with endurance. (I find that for finishing a book quick, it's better to be a tortoise than a hare.)

I read nonfiction and fiction like this. Math heavy texts aren't well suited for it, nor books with many charts and tables, but except for a few cases like that it's very adaptable. Modern TTS even handles weird names in fantasy novels surprisingly well.

Re:Why books don't work (2019) by keenmaster on Tuesday September 22, 2020 @03:49PM (#24559003)
750 wpm is extremely high. I hit 420 wpm on low complexity texts and slow down to 380 wpm at higher complexity using TTS. However, which TTS voice I use has a huge impact. Are you using one of those fancy AI TTS voices with cloud processing?