4 ms·
> Always aim for those 250ms, everywhere Erm no. that number varies depending on the context. For instance, the rule of thumb for UI lag on embedded devices is
by mindslight 8y ago
> Always aim for those 250ms, everywhere
Erm no. that number varies depending on the context. For instance, the rule of thumb for UI lag on embedded devices is around 10ms to feel "instant". Which is why the current crop of surveillance devices feel like cheap junk, because their developers shrugged off that rule in favor of using latency-inducing technology stacks meant for servers.
But not everything can be immediate either. For example, I'll take issue with build time. Sure if you're working with something that can get it down to near instantaneous that's great. But there's also a virtue in needing to plan the change you're making and what you expect it to do.
- maccard 8y ago> For example, I'll take issue with build time. Sure if you're working with something that can get it down to near instantaneous that's great. But there's also a virtue in needing to plan the change you're making and what you expect it to do. And I'll take issue with this too - my current work project takes about 4 minutes to _link_. That's the absolute quickest I can get. There is definitely a ride ground, and in my experience that middle ground is somewhere around the point of "do I check email/slack/hn when I hit build"