3 ms·
This assumption is quite accurate if the machine is under a relatively constant workload, which it often is. The time remaining is quite accurate in my experien
by mikeash 10y ago
This assumption is quite accurate if the machine is under a relatively constant workload, which it often is. The time remaining is quite accurate in my experience as long as I keep on doing whatever I'm doing. If I'm programming for hours, I'll get about what it says. If I'm playing a game for hours (well, a while, it doesn't really make it to hours with games) then I'll get what it says. It'll only fail if I look at the estimate after programming for a while and then assume it'll last that long while gaming, or vice versa. But, that's easy to avoid, and that doesn't diminish the usefulness of the estimate in the scenarios where it is valuable.
"A user seeing a 3 hour estimate (that is probably wrong per the reasons above) when they are doing nothing that seems energy intensive and concluding that their machine is broken is the problem that Apple is trying to solve here."
I'm sure you're right, and this is a typical Apple move recently. Remove a useful feature because the bottom quartile of their users can't handle it. Never mind the rest of us who can.