If only we'd chosen 1944-12-02 08:45:52 as the Unix epoch, we could've combined two doomsday scenarios into one and added a really boring scene to that Roland Emmerich movie.

[–] Tja@programming.dev 23 points 2 weeks ago (2 children)

But that's not a solution, it's just postponing the problem!!1!one

[–] AnarchistArtificer@lemmy.world 11 points 2 weeks ago (2 children)

"it's just postponing the problem!!1!one" The thing of including a "one" to make the irony of your exclamation abundantly clear is a delightful bit of internet-ese. I always find it funny when I see it

[–] teawrecks@sopuli.xyz 3 points 2 weeks ago

For me the giveaway was 2^64 being 1.8*10^19 years from now.

[–] Tja@programming.dev 2 points 2 weeks ago

Thanks! I find it nicer than including "/s" at the end :)

[–] Rhaedas@fedia.io 11 points 2 weeks ago

True, but only if the latest theories on Big Crunch being back on the table don't hold up. Debian ought to not only push out 64 bit time, but place "now" right in the middle to cover any discoveries of an older universe. Hell, they ought to do that and make it 128 bit, to cover anything.

Exponentials can be profound when you grasp them for that fleeting second.

[–] over_clox@lemmy.world 15 points 2 weeks ago (3 children)

'...(potentially setting time back to 1900)...'

From my understanding, unless I'm mistaken, wouldn't the 32 bit time reset back to 1970 after the overflow/rollover?

[–] fargeol@lemmy.world 24 points 2 weeks ago (1 children)

https://en.wikipedia.org/wiki/Year_2038_problem

Timestamps that use signed int will go back to 1901 (-2,147,483,647)

[–] over_clox@lemmy.world 12 points 2 weeks ago

Oh shit, I missed that part, I always thought it was an unsigned int.. 🤦‍♂️

Well today I learned 👍

[–] schnurrito@discuss.tchncs.de 7 points 2 weeks ago (1 children)

you're wrong, but so was the article, so I guess that cancels out :D it's late 1901

[–] eah@programming.dev 17 points 2 weeks ago (1 children)

There are 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors.

[–] glimse@lemmy.world 1 points 2 weeks ago

That's just a really solid joke.

[–] data1701d@startrek.website 10 points 2 weeks ago

The actual transition happened ages ago - 2024 or so. A bunch of transitional packages in Testing and Sid had -t64 appended for a while.

[–] Ephera@lemmy.ml 10 points 2 weeks ago

Hmm, Debian and other long-term support distros are kind of in a tricky position with problems like these. On the one hand, they don't want to break things, so they'll often make changes like these relatively late. But on the other hand, someone might still run a current version of the distro in 2038, so they actually want to solve it as early as possible, too.