Earlier quoted context omitted.
I don't think that's too crazy. Seconds are serial, babies are parallel :)
Yet while one woman can generate 1 baby in 9 months, 9 women can't do it in 1 month
The Unix timestamp will begin with 16 this Sunday
101–110 of 214 posts
Re: The Unix timestamp will begin with 16 this Sunday
#102Re: The Unix timestamp will begin with 16 this Sunday
#103Earlier quoted context omitted.
I'm always left wondering how something like this could happen. I kind of get Y2K and stuff like overflows ... but this one? Really? Did someone put a regex like /^15... to "match" dates?
Yep, that's exactly what Splunk have done - scroll down the release notes linked to by the grandparent and the faulty regex is shown. What's super daft is the proposed fix is only a further sticking plaster, adding support for the 16... range (and the 2020s decade) rather than all future dates. So in a couple of years a further patch will be needed...
Re: The Unix timestamp will begin with 16 this Sunday
#104I remember staying up late (UK) at the Billenium (2:46 AM Sunday Sep 9th 2001), thinking that was bound to be the most newsworthy event of the week, watching the seconds tick past on a "while(sleep 1); do date" loop, with slashdot in one window, IRC in another, all running on an enlightenment window manager. 500M seconds later I was in Washington DC in a hotel, watching it tick up on an rxvt on my laptop, with HN in…
(guenine curiosity) Why do you wait for these events ? Myself I consider these to be complete non-events.
It's an arbitrary thing people do for fun.
Re: The Unix timestamp will begin with 16 this Sunday
#105Earlier quoted context omitted.
There is a very good reason to eventually abandon it: leap seconds. Unix time goes back one second whenever there is a leap second on Earth. It's extremely weird and IMHO completely ruins the purpose of a timestamp, but it's a compromise for backwards compatibility, since Unix time was created before leap seconds. This hack ensures that the number of seconds in a day remains fixed, an assumption of many systems at th…
Isn't a second just how long light takes to travel 299,792,458 m? Also, "since Unix time was created before leap seconds." I found this interesting for the simple reason I've never spent any time thinking about Epoch vs Leap Second histories.
Re: The Unix timestamp will begin with 16 this Sunday
#106Earlier quoted context omitted.
There is a very good reason to eventually abandon it: leap seconds. Unix time goes back one second whenever there is a leap second on Earth. It's extremely weird and IMHO completely ruins the purpose of a timestamp, but it's a compromise for backwards compatibility, since Unix time was created before leap seconds. This hack ensures that the number of seconds in a day remains fixed, an assumption of many systems at th…
Isn't a second just how long light takes to travel 299,792,458 m? Also, "since Unix time was created before leap seconds." I found this interesting for the simple reason I've never spent any time thinking about Epoch vs Leap Second histories.
Re: The Unix timestamp will begin with 16 this Sunday
#107Earlier quoted context omitted.
AFAIK, there is no canonical time in relativity. There is the "local time", which is what your wristwatch shows, and the "time in place X", where X can be Earth, Mars, or some spaceship. These times might not be in sync, and they might even be distorted. Because, if place X is moving relative to you at a significant percentage of lightspeed, their seconds will be longer. Also, the further X is, the blurrier the conce…
If relativity don’t allow time travel doesn’t it make time canonical? A clock on Earth from telescope might look jumpy but only in forward direction after compensating for distance I think
Re: The Unix timestamp will begin with 16 this Sunday
#108Earlier quoted context omitted.
2037 is a potential overflow, I believe. I imagine only pre 2000 systems would likely be affected.
Only pre 2000 systems? I'd love to live in your dream world. Last I looked, plenty of fixes were trickling into the kernel in 2014. I wonder how many of those made the long backport to stable. Let alone all those 2.6 kernels (and older!) in the wild. And all your 32-bit devices are probably gonna have a bad time.
Re: The Unix timestamp will begin with 16 this Sunday
#109Earlier quoted context omitted.
Isn't a second just how long light takes to travel 299,792,458 m? Also, "since Unix time was created before leap seconds." I found this interesting for the simple reason I've never spent any time thinking about Epoch vs Leap Second histories.
And meter itself is defined as the length of the path traveled by light in vacuum during a time interval of 1/299,792,458 of a second. So it's cyclic and doesn't make sense outside the earth reference frame Edit: since 2019, 1 second is defined by taking the fixed numerical value of the caesium frequency ∆νCs, the unperturbed ground-state hyperfine transition frequency of the caesium-133 atom, to be 9192631770 when e…
> realisation of the metre is usually delineated (not defined) today in labs as 1579800.762042(33) wavelengths of helium-neon laser light in a vacuum
Re: The Unix timestamp will begin with 16 this Sunday
#110Earlier quoted context omitted.
With Earth's day length becoming irrelevant, the 24 hour clock becomes irrelevant too, and the length of the sleep cycle may shift. We could eventually arrive at stardates with one starday being 100000 seconds. Of course, that would be just as arbitrary as simply keeping the 24 hours of 60 minutes each.
Humans have a remarkable circadian rhythm that does a pretty good job at defining a day as “24 hours.”
http://www.chronobiology.ch/wp-content/uploads/publications/...
They were very limited, though. We do not really know what would happen on a spaceship that changed its day to 100 000 seconds and subjected the crew to this cycle for months or years.
Given how adaptable people usually are to external influences, I would guess that some adaptation would take place.