Re:Hexadecimal clock counting down to 2038 problem
by thaumasiotes on Sunday September 17, 2023 @09:51PM
(#37551286)
> Most developers making these decisions now will be close to a 100yo in 2199.
We're giving people too much responsibility too young.
Re:Hexadecimal clock counting down to 2038 problem
by NeoTar on Monday September 18, 2023 @04:33AM
(#37553697)
We’re definitely giving negative seventy year-olds too much responsibility.
Re:Hexadecimal clock counting down to 2038 problem
by thaumasiotes on Monday September 18, 2023 @07:35AM
(#37554845)
On the other hand, the ability to communicate with people several decades before they're born should have promising implications for the in-much-higher-demand ability to communicate with people after they've died.
Re:Hexadecimal clock counting down to 2038 problem
by dralley on Sunday September 17, 2023 @10:14PM
(#37551441)
This is what happens when tech companies start looking down on anyone over the age of 30.
Re:Hexadecimal clock counting down to 2038 problem
by oh_sigh on Monday September 18, 2023 @12:00AM
(#37552081)
Do people under 30 care about an extra 2 bytes in a date object?
Re:Hexadecimal clock counting down to 2038 problem
by numlock86 on Monday September 18, 2023 @12:31AM
(#37552257)
Probably, as a lot of people from the current TikTok generation might lack the attention span to read more than two digits, or rather four digits till the end. Embedding some random game's gameplay and audio into your financial export to keep them engaged would increase the size by a couple of magnitudes, too.
Re:Hexadecimal clock counting down to 2038 problem
by Phrenzy on Monday September 18, 2023 @10:28AM
(#37556585)
"There are 5 differences between these two spreadsheets. Can you find them all?"
Re:Hexadecimal clock counting down to 2038 problem
by patmcc on Monday September 18, 2023 @02:55AM
(#37553109)
Sure, but the cost of 2 bytes is a lot different now than it was in 1950 (or 1970, or whatever). Store the full year.
I dont think this means people have forgot history, rather, I think people make tradeoffs. You trade off size/space/ease for long-term disruption. Most developers making these decisions now will be close to a 100yo in 2199. It will not be their problem, or even their childrens' problem. Possibly their grand-children's problem.
Alternatively, I could argue that the life of most systems is short enough that 80yrs is too long a horizon to worry about the problem.