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

Careful – this would also entail midnight UTC happening during the waking hours of quite a lot of people (everybody not living near wherever your new meridian ends up). If you keep the calendar date coupled with UTC, this consequently means that the calendar date changes during the waking hours, which I suspect will end up terribly confusing – for almost everybody, the natural term of reference will still remain the solar day, and so having one solar day split across two calendar days isn't exactly intuitive.

Plus anything that currently is only specified at the granularity of days would need to start being specified with exact starting/ending hours, because otherwise you'd end up with strange things like public holidays starting and ending at 11 o'clock solar time, because that's where midnight UTC happens to lie at your location. Or of course you could make a local law that anything that's specified at the granularity of a day or coarser is presumed to happen at a certain UTC time which corresponds to a more sensible value for midnight based on the local solar time, which means basically reintroducing time zones through the back door…



If you did UTC for coordination you would still have access to solar time. You could have the real thing that changes every day. Then if you wanted to start work half an hour after sunrise at the place of work then you would just do that based on whatever that worked out to in UTC. All the advantages of DST but better. No sudden discontinuities. No time zones required.




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

Search: