Nitpick: In the table where they break it down by category, it seems implied what percentage of each demographic says they don't use the internet (e.g. 25% of people 65+), with no mention of what fraction of non-internet-users are 65+. Both numbers would be interesting!
Absolutely. I wish Google would do simple, sane routes by default, emphasizing roads that were meant to be thoroughfares. I feel bad, and carsick, treating a quiet and winding neighborhood like a highway. And I hate all the traffic that goes along my residential side road presumably due to Google Maps.
"The program does not continue until the remote end receives the corresponding HTTP response. In the initial browser.go call, for example, the remote end will only send its response once the browser has finished loading the requested page."
I think this should read "until the remote end SENDS the corresponding HTTP response", or "until the LOCAL end receives the corresponding HTTP response."
I will pay for it because it's a really good product and I want to have it. I agree that the fee doesn't guarantee Google will always keep the product around, but it certainly seems to signal some investment in Google Photos.
What do "dev question" and "user question" mean? Are these support questions that get asked using a GitHub Issue as the medium, rather than bug reports?
Understandable. The meaning is easy to grasp intuitively if you've studied Latin for a semester or two and happen to know the word "pulchra." If not, I'm having trouble thinking of any cognates in English that are in any kind of common parlance.
Protocol buffers solve most of the issues mentioned by people here, on top of being typesafe, space efficient (no need to encode key names because everything is an ordered struct), and having great tooling.