GlassHouses wrote:Imagine that a government would realize that a lot of people live according to schedules that follow a time standard, that is, according to clocks that are all kept synchronized; that during summer, the sun rises earlier and sets later; that half of the extra daylight time of summer days gets wasted, by people being woken up by the sun, but not having to go to work yet.
Where I live we get around six hours of daylight in the winter, and people who work normal office hours have to get up long before sunrise. In the summer we hardly get any night at all, and there's no need to save any daylight. Farther north from here there are cities north of the Arctic Circle. They get no daylight at all in the winter and no night in the summer. Being woken up by the sun doesn't work at these latitudes. Those who need darkness to be able to sleep have to keep their bedroom dark with blinds or curtains to get any sleep in the summer.
Jumping only one hour is utterly pointless to us. If we would try to synchronize our clocks with the sunrise, then we'd have to change them many hours back and forth, a little bit at a time, and by different amounts in different parts of the country. That would be downright ridiculous, as I hope most people can understand. We have to do the time jump ritual anyway, to synchronize our schedules with the rest of the EU, or whatever the government's current excuse is. Some people's schedules are even so unlucky that every March, just when the sun begins to rise around the time they have to get out of bed, then the "daylight saving" begins, and so their alarm clock starts ringing before dawn again.
GlassHouses wrote:[...] with no other organizational hassle being required [...]
The developers of PHP-FPM seem to have heard that log entries should include the timezone, so it writes the timezone in its logs. The political zone
, that is, not the offset from UTC:
Code: Select all
[07-Jul-2017 21:53:36 Europe/Stockholm]
Any program that tries to collate those logs must look up the zone in the timezone database to get the offset, and even then it's still ambiguous for an hour once a year. But apart from that, yeah, no other hassle.
Except, that is, for the extra programming work I've had to do to ensure that various programs don't overwrite the file they wrote an hour earlier when the clock jumps backwards. But once the programming is done there's no other hassle.
Although, I have at times received meeting invitations sent from Outlook, that specified the timezone as UTC+01:00 along with a list of cities that were in UTC+02:00 at the time, leaving me to wonder which timezone the meeting time was actually given in. Sometimes there has been a notice included that the stated timezone doesn't take daylight saving into account. Gee, thanks for the warning, but that still doesn't tell me whether I should believe the offset or the list of cities. But once I've asked the sender personally what time the meeting will be, it doesn't cause any other organizational hassle.
Well, not quite. Some colleagues of mine were once preparing for a teleconference that was going to begin in 15 minutes, when they suddenly found out that they were 45 minutes late for the meeting. They were unaware that the USA had recently "sprung forward", and I bet the Yankees were equally unaware that the EU hadn't done its jump yet. I think it very likely that the meeting had been booked through Outlook. But except for that there's been no organizational hassle.
Well there was that evening when I went to the communal laundry room to take my clothes out of the washing machines, only to find the machines dead and the clothes soaked in water and detergent. Apparently the power was cut automatically to prevent people from running the machines at night, and nobody had adjusted the timer switch for the latest time jump. I had do take my clothes back dripping wet, leaving a trail of water through the corridors, and rinse them in the bathtub to get the detergent out, and I'll never again book the last evening block in the laundry room.
But other than that, sure, no hassle.