3 ms·

(not the person you're replying to): From what I heard it has something to do with future proofing dates. I don't know how it's future proof, but that's what I

• Joker_vD 2y ago
  So that when year 99999 ends, the Y100K bug can happen, I guess. No idea why having fixed-length 5- (or even 6-) digit strings for years is preferable to normal, variable-length decimal notation we use for numbers: 48, 112, 988, 1122, 2024, etc. The year is a number, treating it as a lexicographically-imbued string only matters for things like ISO 8601 (20240724T vs. 020240724T) but even then, it's already properly ordered: both "99991231T" and "099991231T" sort before "100000101T". But hey, everybody has their small idiosyncratic pet peeves: I've ran twice into the same person here on HN who just can't stand term "x64" because it's "unofficial", but somehow refuses to use e.g. "EM64T" for it as well.
  • kragen 2y ago
    as long as they don't go around 'correcting' your comments that seems okay?
  • ForOldHack 2y ago
    The Y100K Bug impacts every single financial transaction, every single transaction communication, and every single spread sheet, and table: When it comes to this, the gods of Y100,000 will simply wish it with an act of will, and it will come about. "Home was a couple of thousand light years away, which distance they traveled instantaneously, by an application of will. " -Joe Haldeman, "The Groombridge Effect"