home.social

#2038problem — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #2038problem, aggregated by home.social.

  1. 👉 Neuer Blog: „time_t Cast Away: Bits über Bord und der Y2K38 Bug ist zurück“

    Die Umstellung auf 64-Bit-time_t gilt als Lösung für das Year 2038 Problem. Doch Direct Casts machen den Fix schnell unwirksam – und schicken uns zurück ins Jahr 1901.

    Auf das Wortspiel bin ich ein bisschen stolz ☺️

    🔗 y2k38.ch/time-t-cast-y2k38-bug/

    #Y2K38 #time_t #CProgramming #Year2038Problem #Y2038 #2038Problem #CastAway

  2. 👉 Neuer Blog: „time_t Cast Away: Bits über Bord und der Y2K38 Bug ist zurück“

    Die Umstellung auf 64-Bit-time_t gilt als Lösung für das Year 2038 Problem. Doch Direct Casts machen den Fix schnell unwirksam – und schicken uns zurück ins Jahr 1901.

    Auf das Wortspiel bin ich ein bisschen stolz ☺️

    🔗 y2k38.ch/time-t-cast-y2k38-bug/

    #Y2K38 #time_t #CProgramming #Year2038Problem #Y2038 #2038Problem #CastAway

  3. 👉 Neuer Blog: „time_t Cast Away: Bits über Bord und der Y2K38 Bug ist zurück“

    Die Umstellung auf 64-Bit-time_t gilt als Lösung für das Year 2038 Problem. Doch Direct Casts machen den Fix schnell unwirksam – und schicken uns zurück ins Jahr 1901.

    Auf das Wortspiel bin ich ein bisschen stolz ☺️

    🔗 y2k38.ch/time-t-cast-y2k38-bug/

    #Y2K38 #time_t #CProgramming #Year2038Problem #Y2038 #2038Problem #CastAway

  4. 👉 Neuer Blog: „time_t Cast Away: Bits über Bord und der Y2K38 Bug ist zurück“

    Die Umstellung auf 64-Bit-time_t gilt als Lösung für das Year 2038 Problem. Doch Direct Casts machen den Fix schnell unwirksam – und schicken uns zurück ins Jahr 1901.

    Auf das Wortspiel bin ich ein bisschen stolz ☺️

    🔗 y2k38.ch/time-t-cast-y2k38-bug/

    #Y2K38 #time_t #CProgramming #Year2038Problem #Y2038 #2038Problem #CastAway

  5. 👉 Neuer Blog: „time_t Cast Away: Bits über Bord und der Y2K38 Bug ist zurück“

    Die Umstellung auf 64-Bit-time_t gilt als Lösung für das Year 2038 Problem. Doch Direct Casts machen den Fix schnell unwirksam – und schicken uns zurück ins Jahr 1901.

    Auf das Wortspiel bin ich ein bisschen stolz ☺️

    🔗 y2k38.ch/time-t-cast-y2k38-bug/

    #Y2K38 #time_t #CProgramming #Year2038Problem #Y2038 #2038Problem #CastAway

  6. The 2038 Problem: A Ticking Time Bomb for Technology

    As we approach a critical juncture in computing history, the 2038 problem looms large, threatening to disrupt systems worldwide. This issue, rooted in the limitations of 32-bit integers, could have fa...

    news.lavx.hu/article/the-2038-

    #news #tech #TechDisruption #2038Problem #UnixTime

  7. The 2038 Problem: A Ticking Time Bomb for Technology

    As we approach a critical juncture in computing history, the 2038 problem looms large, threatening to disrupt systems worldwide. This issue, rooted in the limitations of 32-bit integers, could have fa...

    news.lavx.hu/article/the-2038-

    #news #tech #TechDisruption #2038Problem #UnixTime

  8. The 2038 Problem: A Ticking Time Bomb for Technology

    As we approach a critical juncture in computing history, the 2038 problem looms large, threatening to disrupt systems worldwide. This issue, rooted in the limitations of 32-bit integers, could have fa...

    news.lavx.hu/article/the-2038-

    #news #tech #TechDisruption #2038Problem #UnixTime

  9. The 2038 Problem: A Ticking Time Bomb for Technology

    As we approach a critical juncture in computing history, the 2038 problem looms large, threatening to disrupt systems worldwide. This issue, rooted in the limitations of 32-bit integers, could have fa...

    news.lavx.hu/article/the-2038-

    #news #tech #TechDisruption #2038Problem #UnixTime

  10. The 2038 Problem: A Ticking Time Bomb for Technology

    As we approach a critical juncture in computing history, the 2038 problem looms large, threatening to disrupt systems worldwide. This issue, rooted in the limitations of 32-bit integers, could have fa...

    news.lavx.hu/article/the-2038-

    #news #tech #TechDisruption #2038Problem #UnixTime

  11. TIL about the #year2038 #2038Problem "Many systems use a 32-bit integer to store the Unix time - the number of seconds since 1 January 1970, known as the Unix epoch. On 10 January 10 2038 at 03:14:07 UTC this count will exceed the maximum value a 32-bit integer can hold, causing an overflow." 👀 :goose_hacker:
    en.wikipedia.org/wiki/Year_203
    #Y2038 #Y2K38 #Y2K38 #epochalypse

  12. TIL about the #year2038 #2038Problem "Many systems use a 32-bit integer to store the Unix time - the number of seconds since 1 January 1970, known as the Unix epoch. On 10 January 10 2038 at 03:14:07 UTC this count will exceed the maximum value a 32-bit integer can hold, causing an overflow." 👀 :goose_hacker:
    en.wikipedia.org/wiki/Year_203
    #Y2038 #Y2K38 #Y2K38 #epochalypse

  13. TIL about the #year2038 #2038Problem "Many systems use a 32-bit integer to store the Unix time - the number of seconds since 1 January 1970, known as the Unix epoch. On 10 January 10 2038 at 03:14:07 UTC this count will exceed the maximum value a 32-bit integer can hold, causing an overflow." 👀 :goose_hacker:
    en.wikipedia.org/wiki/Year_203
    #Y2038 #Y2K38 #Y2K38 #epochalypse

  14. TIL about the #year2038 #2038Problem "Many systems use a 32-bit integer to store the Unix time - the number of seconds since 1 January 1970, known as the Unix epoch. On 10 January 10 2038 at 03:14:07 UTC this count will exceed the maximum value a 32-bit integer can hold, causing an overflow." 👀 :goose_hacker:
    en.wikipedia.org/wiki/Year_203
    #Y2038 #Y2K38 #Y2K38 #epochalypse

  15. TIL about the #year2038 #2038Problem "Many systems use a 32-bit integer to store the Unix time - the number of seconds since 1 January 1970, known as the Unix epoch. On 10 January 10 2038 at 03:14:07 UTC this count will exceed the maximum value a 32-bit integer can hold, causing an overflow." 👀 :goose_hacker:
    en.wikipedia.org/wiki/Year_203
    #Y2038 #Y2K38 #Y2K38 #epochalypse