Zupa Rybna
David BuchananUNIX timestamps were the biggest innovation in timekeeping since the 1st of January, 1970
Jim the U+1F9A6 (Otter)@retr0id At 0000 GMT
🏳️⚧️NotPike🍀
Wolf480pl@retr0id which is basically since forever
Ludovic Archivist Lagouardette@retr0id Unix timestamp as as good as keeping time as a grandma clock, they are not even actually time, time never goes backwards but Unix timestamps do and give every engineer nightmares. Unix timestamps burn your eyes and brain, violently making what should be a relatively simple exercise of physics a philosophical experiment about what constitutes time a and if a clock that is wrong once a year would destroy your life, would you use it. And people used it and discovered that yes, IT DOES
Bart Groeneveld@retr0id Until the 30th of June 1972, when they decided to use the same timestamp for a leap-second and the second before, yielding negative time progress when using sub-second precision.
(Edit: I am not sure when they decided/changed this. I am just referring to the first date that has a leap second.)
Rob Pickering@retr0id So glad I'm going to be properly retired well before January 2038. That will truly be the end of an epoch.
spv@retr0id they really zeroed in on the issue then
I love this, so I
(mandy, she/her)@retr0id Somehow I feel the need to RIP SunOS and AIX (wait! It Lives!!).
(Back in the day I was writing for a small company named DSET that wrote software for phone switches/networks and that always included OS compatibility. Linux was a baby then. Sigh.)
Third spruce tree on the left@retr0id They are totally epoch
Bill Kelly (he/him)@retr0id I'm rembering when Control Data had to put in and emergency software fix because they used a date far in the future, unfortunately some of their computers lasted until that day!