17 ms·
> Presumably there are good reasons to have it That's not a good reason to keep a feature ever. Given the context, browsers are ultimately a user's tool, not
by cptskippy 10y ago
> Presumably there are good reasons to have it
That's not a good reason to keep a feature ever.
Given the context, browsers are ultimately a user's tool, not the developer's and the validity of APIs should be gauged by how useful they can be to the end user. If you can't demonstrate a valid use-case for the end user then there's no business having the API.
- dspillett 10y ago> > Presumably there are good reasons to have it > That's not a good reason to keep a feature ever. I'm not sure I understand you there. If there are good reasons for it existing (as I presume there are) then surely that is a good reason for it to be kept? > If you can't demonstrate a valid use-case Perhaps a full-screen kiosk application needs to indicate battery level (because any OS indicator is hidden? Though admittedly this is not going to be a common need. Another use would perhaps be to turn off "excess" animations in a game when the battery is low.
- cptskippy 10y agoThe problem is that you're presuming there's a good reason or valid use case. The existence of feature or API is not evidence that it's warranted or even a good idea. My point is that you need to scrutinize things a little more and not just trust that there's a good reason for something, especially if it looks problematic.