News for hackers. Stuff that matters.
Re:Linux 5.6 is the most exciting kernel in years by SlowRobotAhead on Sunday February 09, 2020 @09:07PM (#22285830)
... I’m struggling to think there was ever a reason to store epoch seconds as signed.

Was there a use case for “we need to pretend to have 65 years worth of system time before 1970?

Re:Linux 5.6 is the most exciting kernel in years by dredmorbius on Sunday February 09, 2020 @09:57PM (#22286063)
From a favourite Reddit thread:

- Why in the hell would a date value-- particularly one that's an offset-- be signed?

- - How were you planning on indicating dates prior to 1970-01-01?

- - - What date before 1970? We just all assume those do not exist.

- - - - "Now you've made me feel old." "How old are you?" "Let me put it this way: when I was born, time didn't exist."

https://old.reddit.com/r/programming/comments/2b4kpg/conspir...

The full context is ... kind of fun:

https://old.reddit.com/r/programming/comments/2b4kpg/conspir...

Re:Linux 5.6 is the most exciting kernel in years by unlinked_dll on Sunday February 09, 2020 @10:37PM (#22286251)
Well if we bite the bullet and use a 512 bit unsigned int we can represent time zero as the Big Bang and we should be good until the heat death of the universe, based on my napkin math. But I'm no physicist or kernel contributor so unsure of the implications.
Re:Linux 5.6 is the most exciting kernel in years by mekster on Monday February 10, 2020 @07:36AM (#22288541)
No way. Do we know exactly when big bang was or that a second has always been a second since then?

We don't want time implementations based on some definition of big bang version 1.1.3 and all other versions as physicians change the definition of time since big bang.

Re:Linux 5.6 is the most exciting kernel in years by apodysophilia on Monday February 10, 2020 @12:34PM (#22291231)
If the big rip theory is correct, then 64 bits will suffice.
Re:Linux 5.6 is the most exciting kernel in years by war1025 on Sunday February 09, 2020 @10:53PM (#22286309)
What happens when we revise the moment of the Big Bang? Maybe need signed 1024 bit just in case.
Re:Linux 5.6 is the most exciting kernel in years by unlinked_dll on Sunday February 09, 2020 @10:54PM (#22286315)
Might as well just make it signed at that point. We'll never need more than kilibit to represent time.
Re:Linux 5.6 is the most exciting kernel in years by throwaway2048 on Monday February 10, 2020 @07:08AM (#22288412)
Instead we now assume dates past 2038 don't exist...
Re:Linux 5.6 is the most exciting kernel in years by dredmorbius on Monday February 10, 2020 @11:19AM (#22290419)
Time is an illusion.

Lunchtime doubly so.

Re:Linux 5.6 is the most exciting kernel in years by Izkata on Sunday February 09, 2020 @10:46PM (#22286287)
Huh, just realized - time ends at pi-o'clock.
Re:Linux 5.6 is the most exciting kernel in years by skrebbel on Monday February 10, 2020 @05:58AM (#22288031)
This is how I usually compute pi.
Re:Linux 5.6 is the most exciting kernel in years by macintux on Sunday February 09, 2020 @10:01PM (#22286081)
I would bet they were more confident someone would want to represent data from the recent past than that someone would still be using their research lab OS in 60 years.
Re:Linux 5.6 is the most exciting kernel in years by zzo38computer on Sunday February 09, 2020 @09:09PM (#22285836)
Well, now we should use 64-bit timestamps, and 64-bit timestamps is I think sensible to be signed, since there shouldn't need a reason for unsigned 64-bit timestamps.
Re:Linux 5.6 is the most exciting kernel in years by 3fe9a03ccd14ca5 on Sunday February 09, 2020 @09:38PM (#22285962)
“In 30 years from now everything will probably be 512 bit and flying cars, right?”
Re:Linux 5.6 is the most exciting kernel in years by SlowRobotAhead on Sunday February 09, 2020 @09:56PM (#22286061)
That’s the wrong thing. It’s not “will this computer still be running” it’s “does the life of this format work over the time people will use it”. If in 2000 we had 512bit and flying cars, Unix epoch still could be the standard.

The first epoch seconds computers aren’t running things anymore. But, it lives on as a standard.

So the issue isn’t “was it a good idea to count seconds starting at 1970”, but rather “why the hell would anyone use signed for a value that can only be positive? ... and then keep doing it once they realized the problem!?”

2105 or 2106 wont be an issue for unsigned. No one will use a 32bit standard much longer let alone in the 30 years leading up to the problem date.