Citation needed yourself. For the claim that people with devices that show the time actively and largely don't want the time to reflect the location's timezone.
Phone, yes.
Laptop, yes. Times are still stored internally, and the timezone represents a localization. And if I go across the world for the weekend I see that locally, it is UTC+10, while entries in a DB are timestamped accordingly. Then I return home and I can look at the clock in my menu bar and see my local UTC-8, and all the while entries in a DB are timestamped accordingly.
I'd love to hear your use case for "if location and correct timezone can be reliably determined, it still should not be adjusted".
He's claiming that the number of people that don't want their time automatically change on their laptops is not insignificant. You really need a citation for that?
I do. One presumes that Microsoft, Apple and other major OS developers did exhaustive UX studies, and that this - "determine my location and set the timezone representation of the clock to that local time, rather than the original" - wasn't something that a significant portion of people felt.
Why do I say this? There are very few use cases I can think of - though I'm happy to be educated otherwise - for doing this differently. In addition, Outlook and Calendar on my Mac both pick up TZ changes and automatically re-render my calendar appropriately.
I really struggle to picture a use case of "I fly from my home in Seattle back to Australia, and yet I want the clock on my menu bar to display a wall-time 18 hours behind my current location, rather than displaying the current time where my eyeballs are at, and changing back upon return".
Actually, I can think of one - the fear that poorly programmed or tested applications may handle this incorrectly. In which case I can understand this desire, even as a facet of "solving the wrong problem"/shooting the messenger.
One presumes that Microsoft, Apple and other major OS developers did exhaustive UX studies, and that this - "determine my location and set the timezone representation of the clock to that local time, rather than the original" - wasn't something that a significant portion of people felt.
Would these be the same studies that Microsoft cites to justify force-feeding Metro to desktop users?
(Shrug) It seems like a no-brainer that people would want their laptop clocks to be correct. The problem is purely technical: there's no good way to ensure that any change made is correct.
Phone, yes.
Laptop, yes. Times are still stored internally, and the timezone represents a localization. And if I go across the world for the weekend I see that locally, it is UTC+10, while entries in a DB are timestamped accordingly. Then I return home and I can look at the clock in my menu bar and see my local UTC-8, and all the while entries in a DB are timestamped accordingly.
I'd love to hear your use case for "if location and correct timezone can be reliably determined, it still should not be adjusted".