Re:The 64 Milliseconds Manifesto
by dahart on Tuesday September 24, 2019 @04:28PM
(#21064290)
> And really, even offline interactive apps have no chance of reacting this fast.
What do you mean? Lots of games run at 60Hz, and lots of games are considered unplayable if they render frames slower than 64ms. You might consider your terminal broken if it took more than 64ms to respond by displaying your input. https://danluu.com/term-latency/
> Try opening TextEdit or Mail - they don't even draw the window frame in 64 ms.
The OS shows you the app is loading. This seems like you're intentionally trying to prove some point and not listen, rather than being open to understanding. Arguing that an app doesn't respond quickly when the app isn't running seems obtuse.
> If we chose our preferences by performance alone,
Nobody said that, so this is another straw man. The post is suggesting that UI & frontend devs use generally accepted interaction principles, and nothing more.
What do you mean? Lots of games run at 60Hz, and lots of games are considered unplayable if they render frames slower than 64ms. You might consider your terminal broken if it took more than 64ms to respond by displaying your input. https://danluu.com/term-latency/
> Try opening TextEdit or Mail - they don't even draw the window frame in 64 ms.
The OS shows you the app is loading. This seems like you're intentionally trying to prove some point and not listen, rather than being open to understanding. Arguing that an app doesn't respond quickly when the app isn't running seems obtuse.
> If we chose our preferences by performance alone,
Nobody said that, so this is another straw man. The post is suggesting that UI & frontend devs use generally accepted interaction principles, and nothing more.