Rick Waldron

I've been getting `ERR_CONNECTION_TIMED_OUT` for two of those links for about an hour. - https://url.spec.whatwg.org/#dom-urlsearchparams-getallname - https://fetch.spec.whatwg.org/#dom-headers-getall --- From the `Headers#getAll` docs on MDN, it appears that the `Headers` class...

> But if there is no object involved, such as sensor.x, then: > ... > There is much less chance to get confused in this case. Yep, that's how J5...

> seems you're suggesting ES6/7 provides enough syntactic sugar to make a gyro.snapshot() Definitely

> Basically, simply getting data from properties is easier than allocating extra object and getting readings to that object every time data is required. This makes usability somewhat less simple....

This is discussed here: https://github.com/w3c/sensors/issues/28 Can you elaborate the privacy issues with the strategy discussed in that issue?

> identifying parameters This should be easy > sets of sensors and their physical position and location I'm not sure we can actually ever know all of this information for...

Ok, thank you for the additional explanation and clarification

IIRC Solution 3 is part of my original proposal? I still think that's the ideal path: The API surface itself describes a clear demarcation between capabilities - instance provides your...

> ... when using addEventListener(), the start() method must also be invoked. When using onmessage, the call to start() is implied. I agree this is very unintuitive and we should...

> Just for kicks changed your first example with a sensor born deactivated Yeah, I can see that it improves this example (one less call in the code), but is...