Comment by Terr_
2 days ago
Not parent poster, but: It creates annoyance and frustration for the end user, it creates new sources of error (especially when the end-user has to do time-conversions) and provides no actual benefits in terms of system correctness.
What problem are you thinking it would solve?
> What problem are you thinking it would solve?
Traveling.
So instead of your settings sometimes being wrong and easily-fixed with a few clicks, you want them to be almost always wrong? :P
Again, I don't understand what pain-point or use-case is motivating this "set your laptop OS to UTC" proposal.
... Well, not unless it's some workaround for flawed software running on that machine, perhaps made by developers that misunderstood the business-domain of time zones.
> So instead of your settings sometimes being wrong and easily-fixed with a few clicks
It can't be easily fixed. Imagine I continuously change the OS's setting to always reflect the local time. Now I read a log of events happened last Tuesday. Was it when I was in Europe or when I was in the US? How should I read those timestamps? Then I compare two timestamps from last spring. They differ a few minutes, but one was before the switch to DST the other was after. Which one happened first?
> you want them to be almost always wrong?
I think "wrong" is relative, isn't it?
> Well, not unless it's some workaround for flawed software
Exactly the opposite: there used to be a SO from Redmond that didn't allowed you to set its internal clock to UTC. I think it's been corrected now.
2 replies →