RetroSearch Browse

Tue Apr 15 17:58:51 CEST 2014 · https://mail.python.org/pipermail/python-dev/2014-April/134035.html

On Wed, Apr 16, 2014 at 1:56 AM, Skip Montanaro <skip at pobox.com> wrote:
> On Tue, Apr 15, 2014 at 10:42 AM, Daniel Holth <dholth at gmail.com> wrote:
>> I wish it was less
>> than 50 milliseconds (0.05 seconds) including running hg, which is the
>> common threshold for "instant".
>
> "Instant" for me is "the blink of an eye," which Wikipedia reports as
> typically between 100ms and 400ms.
> <http://en.wikipedia.org/wiki/Blink> If you blink, you've missed
> Python 2.7 startup on a relatively modern machine.
>

400ms feels glitchy. 100ms is the absolute maximum for immediate
interaction. If I can sense a musical beat between doing something and
seeing its result, it's not instant.

And if there's a comedic beat between them, it's... laughably slow.

*dives for cover*

ChrisA

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2014-April/134035.html below:

[Python-Dev] Mercurial sluggishness (was: this is what happens if you freeze all the modules required for startup)