Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

In both cases, you need a location to solve the types of problems humans want to solve. A hypothetical: is now an acceptable time to call a tech business in Asia from the US?

- With timezones: I need timezone (location). Generally I can call 9am to 5pm.

- Without timezones: I need location so I can figure out the range of times people typically work in that area (perhaps it might be 11pm to 7am).

And you're back to solving the same problem, just in a more complicated way with no helpful conventions.

In a world with timezones, if your uncle is on the Internet and says "call me at 13h30" but doesn't tell you where he is, you can't call him, because you dont't know when is 13h30.

Nobody who's used to communicating across timezones has this problem. After being bitten in the ass a few times you learn to say "Call me at 3pm eastern" or whatever. The no-timezones cure is way worse than the timezone disease.



> And you're back to solving the same problem, just in a more complicated way with no helpful conventions.

Not more complicated, exactly the same amount of complicated. You can add the conventions.

> After being bitten in the ass a few times you learn to say "Call me at 3pm eastern" or whatever.

And then you still screw it up because DST changes a week later in one country or another, or some such. Even when you do it frequently, it's not a solved problem by any means.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: