Unix Year 2038 problem and the art of underestimating
Jim and Wolf discuss the Unix Year 2038 problem, where Unix's 32-bit signed timestamp, representing seconds since January 1, 1970, will overflow on January 19, 2038. This causes negative values, breaking file/time comparisons in software. They compare this to the Y2K bug, attributing it to storage constraints of the era like punch cards and early hard disks.
Jim argues these were reasonable trade-offs then, not negligence. They also discuss other engineering decisions made based on measurement rather than feeling, which hold up better over time. The episode covers the DJ10K problem, where stock ticker fields would break when the Dow reached 10,000 in 1999, and how the 2038 overflow has been addressed with 64-bit systems.
They examine database timestamp storage, noting Postgres' 64-bit timestamptz, MySQL 5-byte datetime, SQLite's lack of native date type, and DuckDB's 64-bit microsecond timestamps. Real-world overflow bugs include Postgres misinterpreting the year 2038, Excel/Lotus' false leap year belief about 1900, Sony PlayStation 3's freeze on Feb 29, 2010, and Microsoft Zune's clock freeze on Dec 31, 2008.
Wolf emphasizes the importance of writing fixable and maintainable software, not code that only the author can understand, highlighting the danger of "job security through obscurity."
Written by urgent.news from Lobsters's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
