235 points | 6d ago | Discuss on Hacker News | Back to Radar
And how they interact with your mouse cursor.
Ingenious!
Thank you Roy. You made my day! :)
Time to build the failover!
> In November 2022, the General Conference on Weights and Measures decided to abolish the leap second by 2035
I think the story goes that when the leap second was standardized in 1987, the wold was much less connected, there were fewer systems, and hence it was practical to keep astronomical time and civil time coordinated.
But this causes so many bugs and difficulties in practice that companies like Google don't perform leap seconds, they do leap second "smearing". But even smearing has issues, since there are multiple algorithms.
Even worse, the Earth sometimes accelerates, and there was a prospect that we might need a negative leap second, which has never been put into practice.
And as daylight savings makes everyone painfully aware, the public can tolerate even hours of misalignment between civil time and astronomical time, and even an hour adjustment.
So if we decide that we can tolerate a whole minute of skew, we need no leap minute for 50-100 years. And if we could tolerate an hour of skew, we'd not need a leap hour for millennia.
Of course, this is all can-kicking. If a leap second is difficult in practice, a leap hour in UTC (not a flip between a daylight savings and standard time zone) would be even more difficult. I feel the eventual solution would be to very slightly adjust the civil second to be shorter, so that the error begins to reduce.
- always use atomic time
- adjust civil timezones as needed to match astronomical time well enough
Somehow, I don’t see most political and contingent timezones lasting long enough to shift by an hour…
Otherwise, it shifts timezones from being 15 minute granularity to 1 second granularity. Not technically impossible, but will definitely make cross-boarder meetings interesting once the discrepancy becomes large enough. I feel the 15 and 30 minute timezones are already bad enough.
If you have an application that needs a precise solar/astronomical time, you need to back out the leap seconds and then apply a more accurate correction already.
Because of this, I think it would be completely reasonable to just move timezones by 1 hour once the adjustment would be an improvement in accuracy--- which I seem to recall can be estimated to take about 4500 years. The adjustment is already compatible with existing software, and infrequent planned changes of this sort already happen for political reasons.
It won't hurt most usages, it will greatly help computer and recordkeeping usage, and precise solar/astronomical time will also be derisked due to fewer snafus with backing out leapsecond or incorrectly applying them.
The issue will become more critical as we deploy more timing sensitive distributed systems, and especially a low cost atomic timekeeping improves.
It seems likely me that some optical clock designed could eventually be miniaturized and give e.g. 1 second per 32 years drift performance (1ppb-- which is what commercially available miniature atomic clocks can already do) in an affordable and power efficient device. Then you could have correction/communication-free time to 'conventional precision'. But if an unpredictable feed of leap seconds is required you can never have that.
Time is such a fickle thing. Every atom in the universe knows what time it is, but between the effects of gravity, the speed of light and some quantum stuff it is amazing that we can agree on this at any level at all. I spent a lot of time earlier this year getting some ultra stable clocks to run without shelling out 5 digits and it was a very interesting little detour. Eventually I settled on an old atomic clock module from a decommissioned cell tower, not quite 'miniature' but small enough (I've seen some of the newer ones and they are incredible). The thing is precise enough to show the day/night deviation in phase from DCF77 to my home a few hundred km away.
https://www.youtube.com/watch?v=ywD5kngMuYM — British Museum - Curious Clocks and Watches through time with Oliver Cooke
https://github.com/wkjagt/apple2_pendulum_clock/blob/main/RE...
> a pendulum oscillates is only determined by its length (and the strength of gravity), while the weight at the end of the pendulum’s rod (which clockmakers call a bob) doesn’t really matter.
This not correct. The period is determined by the distance from the fulcrum to the centre of mass. The position of the bob does matter. On my grandfather clock there is a small screw that adjusts the position of the bob and hence the length of the pendulum so that you can regulate the clock.
The pendulum in the clock colloquially called Big Ben is regulated by adding or subtracting from a stack British pre-decimalisation one penny coins. However in this case they are placed at the top of the bob not at its centre of mass so adding a penny shortens the pendulum by moving the centre of mass of the bob up
Comments are loaded live from Hacker News and are not stored by Mid or Real.
brightbeige 4d ago on HN
seemaze 4d ago on HN
As an aside, there is a fascinating lineage betewen mining silver and the birth of the Dollar in this region[0], to the establishment of precision horology[1], and thus luxury timepieces.
[0]https://en.wikipedia.org/wiki/Ore_Mountains
[1]https://nomos-glashuette.com/en/watchmaking/watchmaking-trad...
flohofwoe 4d ago on HN
[0] https://en.wikipedia.org/wiki/Wismut_(company)
[1] https://en.wikipedia.org/wiki/Free_Republic_of_Schwarzenberg
tssva 3d ago on HN
Edit: I forgot to mention that we have a NOMOS in the family. I gave my daughter a deep pink NOMOS Club Campus when she graduated high school.