News for hackers. Stuff that matters.
Re:Permanent Daylight Saving Time? Florida Says Yes, but It’... by bena on Thursday March 08, 2018 @04:40PM (#16547880)
It's a huge problem. Your "system time" proposal is already the way things are done.

But people like to know when they did something based on their own clock. Already that one hour shift causes goddamn headaches in showing the proper time to the user for past events.

Now instead of just figuring out if we're across one threshold or another and adjusting another hour, we have to figure out what time of what day it was and figure out what the offset was at that time?

No. Just get rid of DST.

Re:Permanent Daylight Saving Time? Florida Says Yes, but It’... by squiggleblaz on Friday March 09, 2018 @01:11AM (#16550073)
Nonsense. The headaches aren't caused by daylight savings. They're caused by incompetently programmed libraries and systems. If I travel to Indonesia for a week, I want my reminders that are set to occur at 4pm to occur at 4pm. But Google decides that they should happen at 4pm - time zone offset in my home location + time zone offset in my current location. It's insanity. Also, it's insanity that there aren't standard libraries to let me say "4pm". And that programmers think timestamps solve all problems. And that you can use a timestamp to represent a day. But these are all issues that need to be fixed even if we get rid of daylight savings.

Deciding there are gradual drifts to standard time on a daily or weekly basis will cause some hassle. But it will not create a new class of problem that doesn't already exist and which doesn't already need to be fixed.

And time is absolutely the kind of problem that needs to be solved with a few standard libraries, rather than every two bit programmer thinking "i can add two hours to this number, it's a piece of cake".