Re: [geofencing-api] Why is geofencing design tied to service workers?

I found a very interesting, and inspiring quote today that I'd like to
 share with you: -

https://twitter.com/jaffathecake
Googler. "I want the web to do everything native can, and fast."

So  can anyone here explain to me how that precludes device/user 
tracking? Or how HTML5 Web Apps can not be available today with the 
same functionality as Uber, Domino's, GrindR, FaceBook, tomtom?

What the hell are you waiting for?

Here's a couple more platitudes to get you through to the next F2F 
plenary junket: -

https://twitter.com/jaffathecake/status/633621917547778048

"The web should look to increase its advantages while reducing its 
disadvantages. Native is doing this too. If the web stops, it dies."

"The web doesn't need to be better than native at everything, it just 
needs to be close enough that the gap in certain areas doesn't 
matter."


-- 
GitHub Notification of comment by RichardMaher
Please view or discuss this issue at 
https://github.com/w3c/geofencing-api/issues/25#issuecomment-187515011
 using your GitHub account

Received on Tuesday, 23 February 2016 03:55:11 UTC