Comments by "Lawrence D’Oliveiro" (@lawrencedoliveiro9104) on "Time… a programmer's worst enemy // The Code Report" video.

  1. We already do. GPS already needs to take General Relativity into account. Because, you know, clocks run slower down here than up there.
    11
  2. 1:40 Are people assuming this 🇺🇸 bill somehow applies to the whole world?
    4
  3. GMT is actually not well defined. If you look at the legal definition, it’s not clear whether they’re referring to UT1 or UTC. Since the two could differ by up to 0.9 seconds, you can see where a problem comes in.
    3
  4. Let the Olsen Database worry about it for you.
    2
  5. Linux system logfiles used to use some idea of a “system” timezone for timestamps. Luckily, systemd does away with this: internally timestamps are stored as UTC, but you can display entries in any timezone you like, by setting your TZ variable in the usual way.
    2
  6. 0:28 While “International Earth Rotation Service” remains a cool name, I don’t think they officially use that any more.
    1
  7. Use the GNU “date” command to check: ldo@theon:~> TZ=CET date -d "now" Fri 18 Mar 2022 23:07:59 CET ldo@theon:~> TZ=CET date -d "+ 2 weeks" Sat 02 Apr 2022 00:08:01 CEST
    1
  8. If your OS manages time as UTC, you can still figure it out. If your OS only keeps track of local time, you’re stuffed.
    1