Skip to content
DevMeme
5310 of 7590
The Y2K38 Bug: A 32-Bit Time Bomb
TechHistory Post #5826 · source on Telegram

The Y2K38 Bug: A 32-Bit Time Bomb

Description

A multi-panel meme humorously depicting the origin of the Year 2038 problem. The first three panels show a dialogue: 'unix kernel can you give me 64 bits for unsigned 64 bit integer?', which the kernel, represented by Tux the penguin, seems to agree to. However, the fourth panel reveals the punchline: 'Actually uses 32 bit signed integer like a BOSS'. This refers to the historical decision in many Unix-like systems to store time as a signed 32-bit integer, counting seconds from the January 1, 1970 epoch. The final, larger panel at the bottom illustrates the consequences: an image of the Y2K bug logo, a rocket labeled 'UNIX 2038' hurtling towards Earth, and the number -2,147,483,647, which is the minimum value for a 32-bit signed integer, representing the moment the clock will wrap around from its maximum value in 2038 back to a date in 1901. The meme is a classic joke for experienced engineers who understand the long-term consequences of seemingly small implementation details and the history of major, predictable bugs in computing

Categories

TechHistory OperatingSystems Bugs LegacySystems LowLevelProgramming

Common Tags

IntegerOverflow UnixCulture OperatingSystems LegacyTech BugsInSoftware LowLevelProgramming TechHistory

Comments

28
Anonymous ★ Top Pick The Y2K38 bug is just the universe's way of telling us that even in computing, you can't live in the present and expect a 32-bit signed integer to handle your future
  1. Anonymous ★ Top Pick

    The Y2K38 bug is just the universe's way of telling us that even in computing, you can't live in the present and expect a 32-bit signed integer to handle your future

  2. Anonymous

    We’ve built planet-scale, multi-region Kubernetes clusters, but time_t still face-plants at 2^31 seconds - turns out horizontal scaling stops at the sign bit

  3. Anonymous

    The real tragedy isn't that we're using 32-bit time_t in 2024, it's that somewhere out there, a critical financial system written in COBOL is being maintained by someone who retired in 2005 but keeps getting called back as a consultant because they're the only one who understands why the date validation function is 3000 lines long and involves leap seconds from the Julian calendar

  4. Anonymous

    The Y2K38 problem perfectly encapsulates the software industry's philosophy: why solve a problem 30 years in advance when you can let it become someone else's existential crisis? Sure, we asked for 64 bits, but the kernel gave us 32-bit signed integers 'like a BOSS' - because nothing says 'future-proof architecture' quite like a time bomb set for January 19, 2038 at 03:14:07 UTC. At least this time we can't blame COBOL programmers; this disaster is pure C, baby. The real kicker? We've known about this since the 1970s, yet here we are, still running critical infrastructure on 32-bit time_t like we're speedrunning civilization collapse. But hey, that's a 2038 problem, and in tech years, that's basically the heat death of the universe

  5. Anonymous

    Shipping time_t as 32-bit was the original ABI mortgage - everyone agreed to refinance to 64-bit “next release,” and now our incident window has a hard SLA: 03:14:07 UTC, Jan 19, 2038

  6. Anonymous

    64-bit kernels, signed 32-bit time_t: the ultimate 'it works on my machine... until 2038' portability hack

  7. Anonymous

    Architects promised 64‑bit end‑to‑end, but time_t stayed signed int - see you at 03:14:07 UTC on 2038‑01‑19 when half the fleet discovers “type safety” in prod

  8. @andreyegoshin 2y

    I rate this pic with 8 out of 9 jpeg jackals

    1. @callofvoid0 2y

      upper texts are 4 lower pictures are 8 and also there are only 9 jackals

    2. @Unomi 2y

      You're using wrong measure instrument. Made special for you new precise one.

      1. @Kirby_POP 2y

        So precise, in fact, That it features 11 grades

        1. @Unomi 2y

          Yes. From 0 to 10.

          1. @Unomi 2y

            from 3 to 10, to be honest cause of telegram jakaling...:)

    3. dev_meme 2y

      You missed that point, this is intentional for that types of degen memes

  9. @mihanizzm 2y

    I always asking why didn't they use at least unsigned 32 bit integer

    1. @CcxCZ 2y

      https://m.xkcd.com/376/

  10. @andreyegoshin 2y

    fixed

  11. @Kirby_POP 2y

    Btw, are they gonna do anything about it or is it y2k all over again?

    1. @chupasaurus 2y

      yes

  12. @GLXBX 2y

    Where nudes?

    1. @nb30ac 2y

      In 2039

  13. @callofvoid0 2y

    see ? all the homies waitin' for it

  14. @Saeid025 2y

    Can someone give some context?

    1. @AmindaEU 2y

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

      1. @Saeid025 2y

        Interesting, the dude that created the code thought to themselves “this code won't be used past 2038, might as well just save some memory...”

        1. @AmindaEU 2y

          or maybe they thought the world would end before that or they would defeat <hostile AI> that way if not sooner or they wouldn't be around to suffer

        2. @CcxCZ 2y

          The code won't be *my responsibility* by 2038. :-]

  15. @Saeid025 2y

    Or the more accurate answer, they just didn't know/care... Maybe they didn't care to actually do the math

More like this

More like this in TechHistory →
TechHistory IntegerOverflow UnixCulture
A Forgotten 'Feature' from Pre-ANSI C

A Forgotten 'Feature' from Pre-ANSI C

TechHistory
Solving the Y2038 Problem with Existential Dread

Solving the Y2038 Problem with Existential Dread

TechHistory
Unix Time Explains Late Computing

Unix Time Explains Late Computing

TechHistory
Use J and K for navigation