32 ms·
"One example would be the the Geolocation API, with more to come[1]." Ugh. Why would they do that ? I can understand that geolocation could be tremendously s
by rsync 10y ago
"One example would be the the Geolocation API, with more to come[1]."
Ugh. Why would they do that ?
I can understand that geolocation could be tremendously sensitive and you absolutely would want to offer the option of SSL ... but why limit it to SSL ?
geolocation is also something that you'd want to hack into and build into things ... and maybe even things with limited processing power and memory.
Wouldn't it be nice to have the option to interact with a geolocation API (over http) with stdio and not include a giant truckload of dependencies and libraries and megabytes of packages ?
- pfg 10y ago> I can understand that geolocation could be tremendously sensitive and you absolutely would want to offer the option of SSL ... but why limit it to SSL ? I think you answered your own question. ;-) > geolocation is also something that you'd want to hack into and build into things ... and maybe even things with limited processing power and memory. Presumably, once your device is capable of running a modern browser such as Chrome or Firefox (which is what we're talking about here), TLS is a drop in the bucket in terms of resource usage. Or were you talking about the server?