2 ms·
You're basically trading your risk for everyone else's. Not that trade effects and compliance aren't a problem, but the point is you're discounting the impact o
by ggm 3y ago
You're basically trading your risk for everyone else's. Not that trade effects and compliance aren't a problem, but the point is you're discounting the impact of the -1 second effect on everything else.
I don't usually "stand with google" on things, but I think this time I stand with google: better to smear, than invoke negative time and time repeats. If need be declare a trading holiday. Or, ensure the smear is within the compliance limits.
- toast0 3y ago> Or, ensure the smear is within the compliance limits. I don't see how you can be within 11.6 μs of UTC and also smear. If UTC requires leap seconds in both directions (as it does) and your time keeping must be very close to UTC, you must keep leap seconds (this isn't too hard, historically FreeBSD has done just fine, although Linux has crashed a few times, and MySQL didn't like it at least once even if your OS was fine; other applications also had issues). And you've got to figure out how to log :60, rather than :59 twice; this is probably harder. Personally, I'd vote for all seconds be the same length, and all days the same number of seconds, and all days the same number of hours. Maybe ocassionally redefine time zones, until the seconds per day is really off. But you know, the powers that be insist that UTC stay close to UT1, and DST is a thing too (different orgs, but still messed up)