New Y2K just dropped - /pol/ (#507612194) [Archived: 1070 hours ago]

Anonymous ID: VB8qJgRtUnited States
6/16/2025, 7:34:22 PM No.507612194
Year_2038_problem
Year_2038_problem
md5: 3b43a5dbd7bd57e9807d6d7b8b614b0c🔍
Is it going to be just like the last one?
Replies: >>507613362 >>507613376 >>507614782
Anonymous ID: CheH3Ov+United States
6/16/2025, 7:35:19 PM No.507612298
>just dropped
i fucking hate zoomers so god damn much. eat shit and die, faggot
Anonymous ID: 0cSnzHIdUnited States
6/16/2025, 7:44:52 PM No.507613362
>>507612194 (OP)
explain this like I'm 5. It makes the decimal go negative?
Replies: >>507614397
Anonymous ID: zKjlCcZ0Denmark
6/16/2025, 7:44:58 PM No.507613376
>>507612194 (OP)
Unlike Y2K this will be a real problem. Lots of legacy code out there relying on signed 32-bit timestamps.
Anonymous ID: zKjlCcZ0Denmark
6/16/2025, 7:54:10 PM No.507614397
>>507613362
Most software measures time as "number of seconds since new year 1970". If you store this in a signed 32-bit integer (a number that can be negative), which is the default and some widespread programming languages, the maximum value is 2147483647. 1970 plus that number of seconds is 03:14:07, Tuesday, 19 January 2038. When that number is hit, it will wrap around to the minimum value you can put in a signed 32-bit integer, which is -2147483648.
Anonymous ID: hIuZ3mpQPhilippines
6/16/2025, 7:57:50 PM No.507614782
>>507612194 (OP)
Does this makes the nukes go off and hit Tel Aviv?