4 ms·
They were sufficiently accurate enough to be useful for a couple of decades. Are we supposed to believe that the release of 10.12.2 marks some watershed moment
by mikeash 10y ago
They were sufficiently accurate enough to be useful for a couple of decades. Are we supposed to believe that the release of 10.12.2 marks some watershed moment where they suddenly became useless?
No, it's just BS. Apple doesn't want people paying attention to it anymore, so they removed a useful feature just to avoid complaints.
The "Apple no longer knows how" bit is obviously a joke. I agree with petty, but it doesn't make them look misinformed.
- abritinthebay 10y agoThey were pretty terrible all through those decades. They're second only to Windows "time remaining" dialogs as a joke. That's a terrible argument.
- mikeash 10y agoNot at all. They assumed a consistent workload, but given that assumption, they were quite good. Programming in a coffee shop, if the estimate said three hours, I'd get about three hours. If I fired up a game and the estimate dropped to 40 minutes, I'd get about 40 minutes. It failed if I took the estimate for one and applied it to the other, but, well, don't do that. I'm getting rather annoyed at people telling me the estimate was useless anyway. I used it!
- mitchty 10y ago> I'm getting rather annoyed at people telling me the estimate was useless anyway. I used it! Indeed, but I think the argument is more: at best it was a current workload time indicator. I'm still on 10.11 but think I might just make a battery power indicator of my own. Been wanting a better one for a while anyway.
- mikeash 10y agoWell, that's my argument. A current workload time indicator is really handy to have.
- mitchty 10y agoAgreed, just trying to apply the principle of kindness to their arguments. What I want for a battery indicator is more a dual battery indicator/workload indicator. Aka, lets say some process goes nuts for 10 seconds, I'd want some sort of "hey this thing started up over here and is using energy like a fiend" alert. But if I were on power then I'd say only do that after 30 seconds or whatever. That and also keep historic power use and tie that into current use and times and it would seem like you could have some really stupid ML/linear regression to figure out: the user normally runs a compile every 4pm, and its 4pm and he's not on power so that means it'll likely use XMah which means based on the power available he's got about... N minutes of power remaining. Still seems a stupidly annoying problem to solve with so many variables.
- coldtea 10y ago>They were sufficiently accurate enough to be useful for a couple of decades. Citation needed. >Are we supposed to believe that the release of 10.12.2 marks some watershed moment where they suddenly became useless? No, it just marks the moment when they were removed. They had been useless for some time now with modern power-saving processors.
- mikeash 10y agoCitation: about two decades of personal experience using portable Macs on battery power. The estimate is quite useful on my 2013 MacBook Pro, which I'm pretty sure uses a modern power-saving CPU. Correction: it was quite useful. Now it's gone.
- coldtea 10y ago>Correction: it was quite useful. Now it's gone. Don't worry, there's all kind of aftermarket crap menubar apps to put it back in.
- op00to 10y agoWas it actually useful? I think I can manage the battery on my tablet and iPhone just as well as I can on my laptop. Neither the tablet or iPhone estimate how long the battery will last, and somehow I do just fine. That tells me that the time estimate is just noise that doesn't actually contribute to the utility of the machine. I'm OK with removing it since it was never really accurate for me. The time estimates did give me anxiety from time to time. What's interesting is since removing the battery percentage label from my phone, I have less battery anxiety there and it "seems" to last longer since I'm less concerned about the actual percentage remaining.
- mikeash 10y agoOf course it was useful. Why would I be complaining about its removal if it wasn't useful to me? I don't do just fine with my iPhone. I have no real idea how long it'll last. I know that if it's nearly full, it'll last "a while" but I can't judge with any accuracy when I'll need to charge it. My approach is to just plug it in at every reasonable opportunity, which ensures it doesn't quit before the end of the day. I don't fault Apple for that. My iPhone rarely sees a consistent workload, so I don't see how any sort of useful battery estimate could be done there. But my computer is a different story. I usually do the same thing with it for hours at a time. Under those conditions, the estimate was both accurate and useful.