5 ms·
Meta has it backwards, because they could've already made another choice. UTC is a representation of the offset. This will always need to be calculated somewh
by poppafuze 4y ago
Meta has it backwards, because they could've already made another choice. UTC is a representation of the offset. This will always need to be calculated somewhere. Much like how the GPS counts the time since the epoch and broadcasts the offset...it can be used or not by the user. Those times are a calibration adjustment. For UTC, that adjustment is a reference to the current status provided by IERS. That's literally the job of UTC.
Meta can simply stop applying a time offset in their reference, use TAI for forensics, and then have a separately calculated time when they need to display in that representation.
...Which is what happens already. System time is seconds since The Unix Epoch. All of those times are calculated and available, and always will be. They chose one of them, didn't like it, and invented a crummy workaround. They could've logged it in TAI and appended the TAI TZ to all their timestamps.
This is being done to work around poor coding choices they made, instead of making the computing fit reality. Basically "We chose smearing, which is a poopstain of tech debt, so we'll fix it by telling the whole world what time it is." That request is loaded with colossal hubris.
They might as well have the second redefined. The real operators do their thing and leave the squawking to those who want to self-identify a poor coders. Because if they don't want to account for a clock that jumps, then they're kicking the can down the road and they want everyone else to join.
Turning it into a Y2K or Y2038 problem is a sad choice of saddling bigger tech debt on the rest of the world.
Calling it mainstream is as much of a narrative as permanent daylight savings time was. The software solutions exist and were deployed (at least throughout Linux and main userspace) by the June 2015 leap.
This is a Facebook problem that they're sloppily handling by pushing it on literally everyone else.
- nullc 4y agoLeapseconds are an everyone problem. You've personally been impacted by disruptions from leapseconds though you might not be aware of it: it's often not even mentioned in coverage the the cause of issues were leap seconds. E.g. https://insidegnss.com/u-s-flights-canceled-as-faa-looks-into-gps-ads-b-system-errors/ https://insidegnss.com/u-s-flights-canceled-as-faa-looks-int... How many times have you had an issue and resolved it by restarting a system or service without ever truly figuring out the cause?
- denton-scratch 4y ago> You've personally been impacted by disruptions from leapseconds That linked article doesn't mention leapseconds; it doesn't explain the cause of the disruptions, other than to note that it appears to be related to certain defective ADS-B systems.
- nullc 4y agoYep, that was my point. The cause was leapseconds: https://www.ainonline.com/aviation-news/business-aviation/2019-06-11/pilots-oems-dealing-collins-gps-issue https://www.ainonline.com/aviation-news/business-aviation/20... (I'm aware of many others, though I'm not totally sure which might be subject to NDA so I'd prefer to use examples from the press)