4 ms·
However, I don't think the battery state needs to be as granular as it is to support those use-cases. A simple boolean hasLowBattery or a much coarser 0%-25%-50
by DashRattlesnake 10y ago
However, I don't think the battery state needs to be as granular as it is to support those use-cases. A simple boolean hasLowBattery or a much coarser 0%-25%-50%-75%-100% enumeration seems like it would have been sufficient.
- zaroth 10y agoIf anything, I would propose the mode should be a user-controlled bit called simply: "LOW" Maybe I request low mode because... I hope you serve me less crappy ads I haven't bought a new phone in 3 years I am running other apps which need more CPU I find too much interactivity distracting or confusing I just want to read black text on a white background I hate your website, but need to visit it for some reason anyway ... I have full battery, but I need to conserve it I have low battery EDIT: Fuck, I just realized, this already exists, and it's called NOSCRIPT. Wait, we could call this LOWSCRIPT!
- deleted 10y ago[deleted]
- vmateixeira 10y agoSo much truth in here... this proposal would be very welcome!
- bentruyman 10y agoGood luck defining "low". Also, coarse percentages of charge provide no indication of the amount of time left of a battery based on current activity. Which is something you would need in the above offline/save example.
- DougWebb 10y agoMaybe a boolean would work. I don't think 0%-25% would work for the scenario I described; 0% is too late to do anything about the low battery situation, and 25% is too soon to worry about it.
- joshkpeterson 10y agoSaid this in another comment, but - maybe an integer between 1 and 100 would be fine. Some granularity, but not enough to identify.