- From: Tobie Langel via GitHub <sysbot+gh@w3.org>
- Date: Fri, 26 May 2017 09:31:09 +0000
- To: public-device-apis-log@w3.org
So this is a rather large debate I'd like to at least loop @rwaldron and @kenchris in. The whole premise of this new API design for sensors has been to provide Web developers with means to more directly interact with the underlying HW sensors, following the precepts of the Extensible Web Manifesto. If we're now instead deciding that we don't really want to give developers lower-level access, and instead only offer them the ability to hint at getting low latency, we're completely failing those principles. Developer who want to muck with sensors at such a low level know what they're doing and will want to control the sampling frequency at the HW level. They won't really care about the reporting frequency outside of handling the data reporting somehow. So agreeing on this is absolutely critical. -- GitHub Notification of comment by tobie Please view or discuss this issue at https://github.com/w3c/sensors/issues/209#issuecomment-304236740 using your GitHub account
Received on Friday, 26 May 2017 09:31:16 UTC