> All this is with ghosting, of course. High quality rendering definitely takes longer, and I get the impression from my reading and observations of a real devi

> All this is with ghosting, of course. High quality rendering definitely takes longer, and I get the impression from my reading and observations of a real device that bandwidth may play a part in that speed limit. You’re talking about a general purpose monitor attached to a PC. How is bandwidth an issue there? The very same computer can push 120 Hz (or more) to higher res screens than the Dasung. It seems very clear to me that the problem is that the e-ink cells physically can’t react in time to show the next frame. The ghosting means they’re pushing it to the limit. If you’re talking about the controller within the display, well that argument doesn’t track. Controllers capable of pushing pixels that quickly work perfectly fine in conventional LCDs, even power constrained ones like an iPad Pro’s. Why not use those? E-readers have been monochrome for over 20 years, not to mention every other limited-colour piece of hardware. Has that not been enough time for software to adapt and libraries to mature? To be clear, I’m not dreaming of a device to run X11, Firefox, and Doom (like the PineNote people seem to want). I want self-rewriting paper. Of course I want software tailored to that experience, not something off the shelf. If I am making any ridiculous requests, it’s 600 dpi screens at that size. I’m sure there are a thousand reasons why that’s a hard engineering problem.