4 ms·
So why not just use UTC everywhere?
by mirimir 10y ago
So why not just use UTC everywhere?
- acdha 10y agoLegacy thinking and practice. Many developers don't realize this is a hard problem, are used to tools with poor time zone support or defaults, over-estimate the cost of a database migration, or otherwise think they can save time by using whatever the local timezone is. In a fair number of cases, this actually works and in the rest people are often so badly buried that they think it's too late to switch.
- wfunction 10y ago> So why not just use UTC everywhere? ...you live your day by UTC?
- mirimir 10y agoI generally do, yes. I'm a consultant, working remotely. Using anything but UTC would be too confusing. Also, I use multiple online personas, and time zone is an information leak.
- wfunction 10y agoOK, well most people don't set their alarms for "12:00 +0000 (UTC) in the morning". They set it for 8:00 AM local time or something. So you're kind of an exception.
- mirimir 10y agoTrue. But still, can one set UTC as the default for time entry in Google Calendar?
- isostatic 10y agoI do for half the year, being British. At work we have two local relevant times in the office - GMT and Europe/London. Some programs are scheduled at GMT (world service), sometimes they're in UK time (national news). Some computer logs are in GMT, some are in local time. It's a right pain - if we were 4 or 5 hours offset from GMT it wouldn't be a major problem, you tend to know roughly what time you're looking at, and you'd only have wall-time or GMT. GMT and BST are too close together to be unambiguous though. Colleagues working in Washington tend to be 5 hours behind regardless, those in singapore are 7 or 8 ahead. Some countries I give up with completely Specified GMT or UTC doesn't always halo as some people assume you mean "time in London". UTC is better in that regard, but it would be easier if UTC was several hours away from civil time.
- oh_sigh 10y agoDaylight savings time still gets screwed up.