3 ms·

A text heavy application where update rate matters is programming. And I would be the target audience for that. Also I would suspect the high refresh rate isn'

by atoav 2y ago

A text heavy application where update rate matters is programming. And I would be the target audience for that. Also I would suspect the high refresh rate isn't the main cost driver here. You can simply refresh eink displays with different methods that offer different trade offs

JonChesterfield 2y ago
I'm not sure update rate is that important. Subsecond sure, but 33Hz seems overspecified for showing ascii that occasionally scrolls a little. Maybe critical for mouse pointer IDEs?
- atoav 2y ago
  In the end it is about latency. A common example for me would be multireplace, where I select a word, ctrl + d through all instances and replace them. The second step will present me with multiple instaces of often wildly differnt usages of one word per second. This being sluggish or unreadable would be a dealbreaker for me, personally. I can imagine that a somewhat responsive display would also be important for vim users.
- qwerty456127 2y ago
  Yes, mouse pointer is among major articles driving refresh rate demand. Code auto completion/hinting is another one. But these are not essential for every workflow, there are many people who don't really need these. The most itchy thing is waiting for a letter to appear on the screen after you press a key - everyone wants this real time but some people still can tolerate a delay.
qwerty456127 2y ago
> A text heavy application where update rate matters is programming. And I would be the target audience for that. I wish you get what you want soon. Nevertheless I would prefer there to be a cheaper option for those who only need to read static documents or watch dashboards of information which doesn't change fast. > You can simply refresh eink displays with different methods that offer different trade offs Needless to say eInk displays aren't meant to refresh the same way classic displays do. Only the regions which actually change are supposed to redraw. 1 Hz doesn't mean the whole panel is fully reset 60 times every minute, only that it takes a second to display a change. Is this what you mean?

by atoav 2y ago

JonChesterfield 2y ago

I'm not sure update rate is that important. Subsecond sure, but 33Hz seems overspecified for showing ascii that occasionally scrolls a little. Maybe critical for mouse pointer IDEs?

atoav 2y ago
In the end it is about latency. A common example for me would be multireplace, where I select a word, ctrl + d through all instances and replace them. The second step will present me with multiple instaces of often wildly differnt usages of one word per second. This being sluggish or unreadable would be a dealbreaker for me, personally. I can imagine that a somewhat responsive display would also be important for vim users.
qwerty456127 2y ago
Yes, mouse pointer is among major articles driving refresh rate demand. Code auto completion/hinting is another one. But these are not essential for every workflow, there are many people who don't really need these. The most itchy thing is waiting for a letter to appear on the screen after you press a key - everyone wants this real time but some people still can tolerate a delay.

qwerty456127 2y ago

> A text heavy application where update rate matters is programming. And I would be the target audience for that. I wish you get what you want soon. Nevertheless I would prefer there to be a cheaper option for those who only need to read static documents or watch dashboards of information which doesn't change fast. > You can simply refresh eink displays with different methods that offer different trade offs Needless to say eInk displays aren't meant to refresh the same way classic displays do. Only the regions which actually change are supposed to redraw. 1 Hz doesn't mean the whole panel is fully reset 60 times every minute, only that it takes a second to display a change. Is this what you mean?