Mastodawn

I wonder just how many systems are going to get confused or choke on my province's new time zone. I guess people have six months notice before it really becomes an issue

Show thread

Klaus Frank Mar 18

@misty

Tbh, I don't understand why not every it system just uses UTC internally and leaves all of the timezone crap up to the fronted as "fancy formatting".

That would solve so many issues that are caused by the systems running in local time and then having to constantly convert it when interacting with other shit that is configured to a different local time...

Show thread

damien 🥖🐈‍⬛🧣Mar 18

@agowa338 @misty i mean, the frontend, whatever it is, still needs to *know* about the timezones so that's just moving the problem

Show thread

Klaus Frank Mar 18

@eramdam @misty

Well it would remove the most annoying problems like e.g. the apple calendar not being able to handle an appointment with start time in UTC+1 timezone and end time in UTC+8 in combination with daylight savings. And then showing the appointment at a different time than MS Teams is showing it.

Show thread

Yoh Deadfall Mar 18

@agowa338 @eramdam @misty, it's a partial solution while the problem is in humanity and in thoughts that time is simple. Look, we have time zones and daylight saving time, and no system handling it correctly. And I even haven't started about realtime and monotonic clocks!

Show thread

Klaus Frank

@yoh @eramdam @misty

Well the main issue is that people using time in file formats and such thought "time is simple". If they assumed it is complex they'd have abstracted it and just normalised it all along...