3 ms·

You've got to be kidding? This has continuously been a huge problem since... y2k? forever? https://www.computerworld.com/article/2529992/zune-chokes-on-leap-y

You've got to be kidding? This has continuously been a huge problem since... y2k? forever? https://www.computerworld.com/article/2529992/zune-chokes-on-leap-year-bug.html https://www.computerworld.com/article/2529992/zune-chokes-on... And the ever looming 32bit problem https://en.wikipedia.org/wiki/Year_2038_problem https://en.wikipedia.org/wiki/Year_2038_problem date stored as an unsigned int(32bit) is fine. It's efficient especially for smaller CE/embeded electronics. Gets us to ~2100? Hopefully most of those systems are dead by then.

setr 5y ago
You’re referring to Unix time, which is generally acceptable (if too small). The GP I think is referring to the art of storing Jan 1, 1970 8:11 as the number 197001010811 —- YYDDMMhhmm format, but as a number rather than a string. Which isn’t really that bad, since it’s ultimately the same as problem as Unix time, but it’s definitely an unnecessarily abusive encoding that’s distinctly worse than Unix time for no real gain