would one timezone/date internationally work?

I already store all my date information in UTC in most systems I build, then convert to local time on the UI based on the user. I'd love a single time worldwide. Time is just a number, I reckon we could adjust. Here we'd be going to work from 10 - 7 instead of 8 - 5. As it is you already have to convert from your time zone to another when doing international conference calls. Sometimes the person on the other side says "we'll call at 7pm"... leaving you to wonder if they mean your time zone, theirs, or UTC? You have to specify which time zone. It would be great to say "we'll call at 7pm", and you both just dial in at 7pm.

I think it would simplify business, and get rid of a lot of unnecessary calculation. You can still work out a time zone difference if you want based on distance (every 15 minutes longitude = 1hr).

It would just be morning in New York at 12:00. "I get to work at 12:00, let's call then". So much simpler than "I get to work at 8am, so because we are at UTC - 4 (Eastern Standard Time), and you are at UTC + 2 (SAST), that's 6 hours difference, so that would be 12pm your time"
 
Personally I prefer noon when the sun's overhead or thereabouts. And midnight should be dark. Personally I don't have the slightest struggle with the current timezone regime, and I deal across timezones daily. Of course I understand that others might find it a challenge.

I like the world with lots of local thingies, idiosyncacies and variations, and would oppose the idea mooted above. Even if implemented, one would still have to do translations and calcs to fit theory-time into "real" solar and sidereal time.
 
Last edited:
shogun said:
I already store all my date information in UTC in most systems I build, then convert to local time on the UI based on the user. I'd love a single time worldwide. Time is just a number, I reckon we could adjust. Here we'd be going to work from 10 - 7 instead of 8 - 5. As it is you already have to convert from your time zone to another when doing international conference calls. Sometimes the person on the other side says "we'll call at 7pm"... leaving you to wonder if they mean your time zone, theirs, or UTC? You have to specify which time zone. It would be great to say "we'll call at 7pm", and you both just dial in at 7pm.

I think it would simplify business, and get rid of a lot of unnecessary calculation. You can still work out a time zone difference if you want based on distance (every 15 minutes longitude = 1hr).

It would just be morning in New York at 12:00. "I get to work at 12:00, let's call then". So much simpler than "I get to work at 8am, so because we are at UTC - 4 (Eastern Standard Time), and you are at UTC + 2 (SAST), that's 6 hours difference, so that would be 12pm your time"
Click to expand...

You got it in one. Time is only a number.
 
shogun said:
I already store all my date information in UTC in most systems I build, then convert to local time on the UI based on the user. I'd love a single time worldwide. Time is just a number, I reckon we could adjust. Here we'd be going to work from 10 - 7 instead of 8 - 5. As it is you already have to convert from your time zone to another when doing international conference calls. Sometimes the person on the other side says "we'll call at 7pm"... leaving you to wonder if they mean your time zone, theirs, or UTC? You have to specify which time zone. It would be great to say "we'll call at 7pm", and you both just dial in at 7pm.

I think it would simplify business, and get rid of a lot of unnecessary calculation. You can still work out a time zone difference if you want based on distance (every 15 minutes longitude = 1hr).

It would just be morning in New York at 12:00. "I get to work at 12:00, let's call then". So much simpler than "I get to work at 8am, so because we are at UTC - 4 (Eastern Standard Time), and you are at UTC + 2 (SAST), that's 6 hours difference, so that would be 12pm your time"
Click to expand...

You got it in one. Time is only a number.
 
Noon and midnight are just words. Your midnight would still be dark and noon would be daylight. Global communication doesn't refer to noon or midnight it takes place at a specific time.

If you called a table a chair it would still be the same thing.
 
Why bother correlating time with the sun anyway? I'll see you guys at 1366532100 seconds after the unix epoch.
 
murraybiscuit said:
Why bother correlating time with the sun anyway? I'll see you guys at 1366532100 seconds after the unix epoch.
Click to expand...

I'd prefer IAT. It doesn't rely on earth's rotation at all. It was initially synced with it, but now runs solely as an atomic clock irrespective of earth rotation. You need to add the accumulated leap seconds to correspond with leap time.

http://en.wikipedia.org/wiki/International_Atomic_Time

There we are, the perfect time system imho.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X