Live data from Hacker News

Time to Dump Time Zones

nytimes.com

171–180 of 555 posts

Re: Time to Dump Time Zones

#171
post #17

Hmm...this is an interesting idea. However, the core of the argument seems to be this: > “The economy — that’s all of us — would receive a permanent ‘harmonization dividend’ ”— the efficiency benefits that come from a unified time zone. But this editorial is pretty light on actually supporting that. The basic argument seems to be that it reduces 'translation costs'. But..does it? What about the benefits of being able…

The NY author convinced me about the Earth time, and you got me back. You are right, a change like this would create other problems, as you cited.

Re: Time to Dump Time Zones

#172
I wish this was about day light savings and the random changing of the time zone. I can live with the different time zones and I think they are even kind of nice, but day light savings changing the current time, is terrible. You could argue it had cost real money (think azure going offline) and think of all the countless other hours people have spent dealing with the change.

Re: Time to Dump Time Zones

#173
post #17

Hmm...this is an interesting idea. However, the core of the argument seems to be this: > “The economy — that’s all of us — would receive a permanent ‘harmonization dividend’ ”— the efficiency benefits that come from a unified time zone. But this editorial is pretty light on actually supporting that. The basic argument seems to be that it reduces 'translation costs'. But..does it? What about the benefits of being able…

This hits the nail on the head. Abandoning time zones would only make sense if there were no more need for time translation. But you'd still need to translate for the sake of biological clocks, and without time zones it would become more challenging to communicate that translation. I would be in favor of doing away with DST and also eschewing AM/PM in favor of a 24-hour clock. I'm surprised this article didn't mentio…

> eschewing AM/PM in favor of a 24-hour clock

Even if we keep AM/PM, we should make it make sense. It should switch when the numbers roll over. Having 11am be followed by 12pm is nonsensical. The fix for this, as any programmer will tell you, is to recognize that 12 is really 0...we've got an off-by-one bug. Midnight should be 0am and noon should be 0pm.

Re: Time to Dump Time Zones

#174

I have huge issues with DST and how we measure time in general (24hours, 60 minutes, 60 seconds?! Who the f* came up with these crazy ass numbers?!). But what bugs me much more is the insane calendar. 12 Months with arbitrary numbers of days. That's just crazy. In the very least we could make it so that January to May have 31 days and the remaining months get 30. ideally we would switch to the positivist calendar. Th…

There are a few proposals to move to a more standardized month, one being the International Fixed Calendar which contains 13 months of 28 days each, and one "year day" at the end of the year which can function as a public holiday.

I think it's brilliant. Will never happen.

Re: Time to Dump Time Zones

#175

Earlier quoted context omitted.

This hits the nail on the head. Abandoning time zones would only make sense if there were no more need for time translation. But you'd still need to translate for the sake of biological clocks, and without time zones it would become more challenging to communicate that translation. I would be in favor of doing away with DST and also eschewing AM/PM in favor of a 24-hour clock. I'm surprised this article didn't mentio…

I get the impression Americans don't use 24-hour clock much. In Europe it's pretty much standard if you want to communicate time reliably. Or am I mistaken about the American love of am/pm?

Unlike most of the imperial system, farenheit, etc, Am/pm seems to actually make some sense with analog clocks/watches. In places where you primarily use 24 hour time I guess you're always just translating from the clock in your head?

Re: Time to Dump Time Zones

#176
post #137

Earlier quoted context omitted.

I get the impression Americans don't use 24-hour clock much. In Europe it's pretty much standard if you want to communicate time reliably. Or am I mistaken about the American love of am/pm?

Your impression is pretty much spot on. We have "military-time" and "24-hour time" available to us in all of our application configurations, but no-one seems to use it. I do because it helps me do time-zone translating transforms to/from UTC in my head more easily, but also because I keep failing to see that little "PM dot" or set the "PM Flag" whenever dealing with times in various applications or alarms. Verbally,…

"Verbally, speaking with USians, 15.00 is always pronounced "3pm"."

It's like that everywhere in Europe. Nobody says 'see you at fifteen'. 24 hour clock is merely for writing things down. I mean it would already be an improvement if the US would catch up with that, just saying that a 24 hour clock isn't said out loud as such. (not disagreeing or anything with you I guess, just adding some information).

Re: Time to Dump Time Zones

#177

Earlier quoted context omitted.

But the current concept of time is also based on the outdated industrial age concept of a 'working day' being 9-5. I doubt many of the people on HN for instance, work those set hours in this day and age. Nowadays it is purely a convenience factor to keep the worker drones in the same hive so they can gather for the next interminable meeting. With the rise of remote working, and other forms of communication tools, no…

For those who live in our Ivory Tower of the software industry that may be true, but the 9-5 concept is not outdated for a vast majority of working humans on the planet. Lets not project our reality onto the rest of the world.

In the US, try 9-6, unfortunately.

Re: Time to Dump Time Zones

#178

Earlier quoted context omitted.

You're correct. We call the 24-hour clock "military time" and basically no one uses it casually.

I do. Granted, I was in the military-I passively hate it when people call it 'military time' (passively meaning I mentally roll my eyes when someone says it), but I've been using it since middle school when I first even learned it was a thing. Mostly because it made sense right away. There are 24 hours in the day. Why are we recycling numbers in our time system? No really, why?

Because there are only 12 major divisions on a clock. An analog clock, that is. It reads the same at 3am and 3pm. So from that pov it only makes sense to call it the same.

Re: Time to Dump Time Zones

#179
post #176
post #137

Earlier quoted context omitted.

Your impression is pretty much spot on. We have "military-time" and "24-hour time" available to us in all of our application configurations, but no-one seems to use it. I do because it helps me do time-zone translating transforms to/from UTC in my head more easily, but also because I keep failing to see that little "PM dot" or set the "PM Flag" whenever dealing with times in various applications or alarms. Verbally,…

"Verbally, speaking with USians, 15.00 is always pronounced "3pm"." It's like that everywhere in Europe. Nobody says 'see you at fifteen'. 24 hour clock is merely for writing things down. I mean it would already be an improvement if the US would catch up with that, just saying that a 24 hour clock isn't said out loud as such. (not disagreeing or anything with you I guess, just adding some information).

Let's meet at 15 o'clock" or "When do you go for lunch?" "thirteen-thirty" is totally daily usage in some places/groups (possibly age-related, since digital clocks here are always 24h and younger generations had more relative exposure to them)
Post reply on HN