The 64 Milliseconds Manifesto

Re:The 64 Milliseconds Manifesto by kevin_thibedeau on Tuesday September 24, 2019 @04:00PM (#21064004)

Will you wait > 100ms for a checkbox to change state? The point is that actions that should be instantaneous need to appear as such within the limits of human perception. Complex operations can take longer.

[ Parent | on HN ]

Re:The 64 Milliseconds Manifesto by dangus on Tuesday September 24, 2019 @04:11PM (#21064110)

No, but that's not what the manifesto says.

Full screen of content within 64 ms.

Sure, I definitely expect a checkbox to do something in < 100ms. Show that its state changed and at the very least show me some kind of loading icon so I know something is happening.

But a full screen of content in 64 ms? Unreasonable, and really a completely undefined unit of measure (what is/how big is a "screen" and how much content can fit within? How do you measure audio or video content? What happens when I'm working with vector graphics that can't possibly render in 64 ms?)

[ Parent | on HN ]

Re:The 64 Milliseconds Manifesto by kevin_thibedeau on Tuesday September 24, 2019 @04:59PM (#21064558)

80's PCs could populate a "screen" in that timeframe. Why do we accept less performance from modern computers?

[ Parent | on HN ]

Re:The 64 Milliseconds Manifesto by dangus on Tuesday September 24, 2019 @05:28PM (#21064825)

This argument (accidentally) completely aligns with mine - this manifesto makes no distinction between complex and simple applications.

There were plenty of applications in the 80s that could not render a full screen in that timeframe. That did not stop those applications from being useful.

(And I honestly think a DOS directory listing can take longer than 64ms to fill the screen)

[ Parent | on HN ]