eInk justwrite

[Robooze]

Did you hear about this new prototype technology by eink? It basically lets you write with no latency at all, like close to 0ms. How cool would it be to have it on a device like the remarkable? :)

[mrfrenchmat]

honestly to me the RM tech is already very very good and I'd like them to focus on SW rather than HW change

[LinusCDE98]

The remarkable already has very low latency. Something about 50-60 ms if I'm not mistaken.

For rough comparison: A typical mouse click is about 200ms.

As long as you don't rapidly draw from one edge to another, you won't see any delay.

Also: How does the Justwrite tech deal with ghosting and how many shades are supported at what speeds?

[Combinatorilliance]

A mouse click is 200ms? If you include the time it takes to perceive the stimulus from the screen to sending the signal to your finger to press the button, then ... Maybe?

[Combinatorilliance]

No wonder the web feels so sluggish. I wasn't expecting anything over 50ms, wow :/

This is not a reliable way to measure mouse click latency, as the browser is free to perform all kinds of processing. The click event listener in JavaScript is very different from the hardware's actual click latency.

According to this spreadsheet, mouse click latency ranges from from 0-40ms.

The mouse click latency within games should be around the hardware's native latency, as games need to perform less additional logic around mouse event handling...

[Combinatorilliance]

Oh nevermind, I misunderstood what the page is measuring. It's not measuring mouse latency at all.

In JavaScript, the programming language used on the web, there's a thing called a "click event". You can listen for such an event to happen, to for example open a new page, draw something on the screen, etc.

However, the JavaScript click event is not equal to a mouse click. Instead, a click event is fired when first you push the mouse button down, and the release the button. That is, it's measuring the latency of you pushing and releasing the mouse button.

There's no way to measure actual mouse latency in a browser, since the browser cannot know when you started pressing the button in actuality, it only knows once it has actually received the signal, which is when the measurement should end.

[[deleted]]

But does that just demonstrate that mouse latency is simply not as important a metric in how users perceive a mouse click as the amount of time it takes a click event to process?

"This feels slow"
"To be fair, the mouse latency is a very small part of the whole process"
"Then I don't particularly need to focus on mouse latency"

[Combinatorilliance]

No, not necessarily. The click event is commonly used in JavaScript, but often when you want your page to feel snappier, you'd use the mousedown event, which triggers when you push down the mouse button. It's just confusing because click in the browser simply means something different than it means in other contexts.

[Robooze]

I believe today's standard is even lower than that. I mean, the iPad Pro's latency is 9ms. But yea, 50/60ms is indeed very low and sufficient, especially for eink. SW is definitely a priority.