[camkego]

Actually, this is a fabulous idea! Today people must communicate time+zone to understand when an event will occur, unless people are assuming the local timezone. The thing is, little business is just local now. Think about the process for scheduling meetings between coastal groups, time+zone information must always be communicated.

I suspect all the time zones are really costing us more work than than they benefit us.

[cdcarter]

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.

[rodgerd]

I suspect the number of people who share the perspective of programmers working across international teams is a lot smaller than the programmers think.

[gooderlooking]

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.

[aninhumer]

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).