Re:Daylight Saving Time Is Terrible: Here's a Simple Plan to...
by cdcarter on Sunday November 03, 2013 @02:29AM
(#6662509)
Actually, I'd say that most business is still local. And making everyone wildly redefine what their even most simple definition of what a calendar day is doesn't seem to be useful.
Re:Daylight Saving Time Is Terrible: Here's a Simple Plan to...
by rodgerd on Sunday November 03, 2013 @02:43AM
(#6662529)
I suspect the number of people who share the perspective of programmers working across international teams is a lot smaller than the programmers think.
Re:Daylight Saving Time Is Terrible: Here's a Simple Plan to...
by gooderlooking on Sunday November 03, 2013 @03:18AM
(#6662582)
Ever hear of someone missing a meeting because it was scheduled for 2:00EST and they thought it was 2:00PST? Ever see an email from an employer, or hear the news reminding you to change your clock this weekend? It's not a programming problem, programmers are just more keenly aware of it.
And it's not really a "problem" at all. Just an idiosyncrasy. Like imperial units.
Re:Daylight Saving Time Is Terrible: Here's a Simple Plan to...
by aninhumer on Sunday November 03, 2013 @09:03AM
(#6663209)
I think a much better idea would be to give UTC time in addition to local time as a standard practice. That way everyone only needs to memorise their own offset, instead of looking up what a particular acronym means every time they need to. (And probably forgetting, if they don't do it that often).
I suspect all the time zones are really costing us more work than than they benefit us.