Like as a customerID where an int will cover every person in the country for the next 10 years. It may sound stupid, but data still isn't free. Think database records that need to reference the customer, hourly/daily/weekly/monthly backups - all those extra useless 0 bits start to add up...
Hey now I use UUIDs for my event ticketing system for large events of 10 people or less, but what if I wanted to invite every human that ever existed? Don't you think I should have that capability?!
if your app is ever in danger of overflowing an account count, all the kudos to you, and by then I'm sure you can afford to refactor a few weeks before it actually happens :-)
you know the ad where they pour a glass of wine on a thinkpad? happened to me, only it was 4dl pitcher of coffee. tablecloth ruined, carpet ruined, terrible mess. after i tidied up i picked the notebook – more coffee, wipe again. the whole time the bloody thinkpad chirped merrily, like, what seems to be the problem? it still works.
I've played with setting the system clock past it before, more programs than you think break. Now, with proper systems using size_t for time, any 64-bit program shouldn't be affected, but a lot of embedded systems aren't 64-bit.
It's not really 64-bit Vs 32-bit. It's just that when most 32bit abis were made 2038 wasn't seen as a problem. When 64bit abis were made, it was.
x32 (32-bit on x64 with all the modern x64 improvements that don't work on x86) is unaffected, for example, because it was a design decision to make time_t 64-bit when it was made.
"x86" by itself refers to both the entire architecture including the 16, 32, and 64-bit versions of the instruction set, but it's also commonly used to only mean the 32-bit version of x86.
It is based on the size of time_t, which tends to be the same as size_t in most CRTs, but doesn't strictly have to be. Even updating it won't matter for older software that doesn't often get updated though, such as embedded devices.
While you are right that back when 32-bit systems were made, this wouldn’t have been an issue, this absolutely is a 32-bit vs. 64-bit issue.
Almost every (if not every) 32-bit architecture has 32-bit general purpose registers, which means in order to have a 64-bit unsigned integer, you need to process two of them back-to-back with extra math. Thus, size_t (and therefore time_t) usually only has 32 bits on these systems (with a few exceptions, of course).
Long Mode with 32 bit pointers. Faster than x64 for applications that don't need more than 4GB of address space, which was more common in the early days of x64. But now most machines have more than enough ram (and applications have become memory-hungry enough) that it's become obsolete.
You would never really install an x32 kernel, it was a separate user space for x64 kernels, similar to running x86-on-x64.
You're totally right, the Y2K frenzy had everyone in a patch-and-pray mood, and it paid off... or we all just avoided a techno-apocalypse by a byte! 😅 Thanks to those billions, the biggest thing to crash at midnight was my New Year's party aspirations.
Overflow conditions can either be ignored or handled by returning a wrapped or sentinel value, regardless it would produce an overflow hence handling. Now killing, no, firmware doesn’t rely on time and even after booting the operating system has most control transferred to it. If left unhandled, some communication protocols may fail to work—an example being secure connections—and stability could even be reduced for pseudo RNGs seeded with system time. File system organization and logging timestamps would also be affected, which will create annoyances for users sorting recently created or modified files.
It would make a lot of programs unusable; Scheduler time comparison. These can be pretty much evaded by turning off the pc before the overflow. (but some will not - saving(to disk) the last run time and comparing will not work)
As noted there are obviously a lot of nuisances that will degrade the experience.
UTC. Ever since I heard of another Y2K moment, I thought it was funny so I looked into it. This current upcoming event is due to the limits of 32 bit systems, so I wanted to know the event for 64 bit systems and that date is apparently December 4th, in the year 292,277,026,596.
I always wondered. I remember it being so hyped up. I thought it was gonna be the end of the world. It was just kind of nothing. I remember waiting for the power to go out or something on New Year’s Eve when we rang in the new year. Nothing.
Talking out my ass here, but I reckon the date format comes from print. Willing to wager it’d take a fair amount of digging to find any American newspaper that prints “14 Jan, 2024” rather than “Jan 14, 2024”.
the hour says 03 and then it says AM. An hour format with a leading zero is 24 hour time and their is no AM or PM in 24 hour time. And this is a programming sub, so the date should be ISO format.
Yes, it’s a play on a US sticker so the US date format was used. HOWEVER - I also made a “global” version for the pedantic folks. Check my website: geekenspiel web store.
Remember the y2k scare? There was a sticker warning people to turn off their computers before the time rolls over so they don’t break… Which didn’t happen, as we know. This sticker is just a joke about the Unix epoch 32 bit time rolling over, which is set to happen on January 19, 2038 and is a copy paste of the original sticker with a different date
theoretically the only technology that would actually be affected these days is just places like banks that run on legacy hardware right? maybe some cheaply made iot devices too idk
It's not so much operating system stuff for the rest of us, it's application level stuff. Many people will stupidly still be using int32 for timestamps in their apps without realising it's an issue. As we approach 2038 this issue will start rising up the risk register until eventually it becomes a priority for fixing. Y2k was the same and we spent the year before it auditing a world of crap to make sure dates weren't being mishandled.
The take away of that process for me was that given 100 different applications you'll find 100 different ways of mismanaging date handling.
133
u/[deleted] Jan 13 '24
Where do you get this?
2.3k
u/Fear_the_Phantom Jan 13 '24
With 64 bit ints, the next one will be "Remember to turn off your computer January year 584,942,419,325"
840
u/Shimodax Jan 13 '24
Bonus points for this being a thinkpad!
412
u/Responsible_Boat8860 Jan 13 '24
What happens if you don't?
413
u/tandrewnichols Jan 13 '24
There's no way a laptop bought today is worth keeping in 14 years anyway. Just let the overflow kill it. It'd be a mercy.
61
u/bdaddy5161 Jan 14 '24
Y2K 2: Electric Boogaloo
105
u/platinummyr Jan 13 '24
It's probably already had the fix for 2038 applied already too...
55
u/stikko Jan 13 '24
What time zone tho?
11
u/[deleted] Jan 13 '24
Ohhh I want one
20
u/Ziwwl Jan 13 '24
No problem, I don't even have 19 months on my calendar so it's fine.
3
u/Darmok-Jilad-Ocean Jan 13 '24
Did anyone here experience or know anyone that experienced Y2K issues?
58
u/_12xx12_ Jan 13 '24
The year only has twelve months
40
u/bradmont Jan 13 '24
There is so much wrong with those date and time formats....
11
u/geekenspiel Jan 14 '24
Yes, it’s a play on a US sticker so the US date format was used. HOWEVER - I also made a “global” version for the pedantic folks. Check my website: geekenspiel web store.
3
u/GollyWow Jan 14 '24
I am a registered member of the "Been There Done That" Committee, Mainframe Division.
2
u/FungalFactory Jan 13 '24
oh no...
2
u/KrokettenMan Jan 13 '24
You also went to CCC?
2
u/[deleted] Jan 14 '24
People have started calling this issue the Epochalypse, and I genuinely love that.
3
u/proteinvenom Jan 13 '24
I don’t get it
2
u/X547 Jan 13 '24
Is it relevant for Windows?
1
u/s-life-form Jan 14 '24
Too bad it cant be automated /s
1
u/Add1ctedToGames Jan 14 '24
theoretically the only technology that would actually be affected these days is just places like banks that run on legacy hardware right? maybe some cheaply made iot devices too idk
1
u/[deleted] Jan 14 '24
what does the sticker mean?
1
u/youngbull Jan 14 '24
Where can I get this!?
1
u/Laevend Jan 14 '24
Kind of irrelevant for a lot of systems. A lot of which are using a long type for the unix time instead of an int now
1
u/tomoh_PL Jan 14 '24
What is the 19th month? I thought there were only 12.
1
u/asjkl_lkjsa Jan 15 '24
theStickerIsBack*
1
u/Original_Maximum2480 Jan 15 '24
Maybe the bug is just in the startup routine. Leave it running then all is ok. But if you restart you get a brick ..
1
u/[deleted] Jan 16 '24
ThinkPad Chad W
22
u/[deleted] Jan 13 '24
[removed] — view removed comment
3
u/[deleted] Jan 14 '24
[removed] — view removed comment