• Jo Miran@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    7 months ago

    I’d start with a 13 month/28 day calendar and planetary time (all clocks set to UTC).

    EDIT: And set the date format to YYYY.MM.DD for the entire world. Americans and Europeans can stop arguing. The Japanese got it right.

  • xmunk@sh.itjust.works
    link
    fedilink
    arrow-up
    0
    ·
    7 months ago

    If you’re not using tz_database or equivalents for literally all date-time logic, if 24 or 60*60 are constants defined in your project… you’re doing it fucking wrong. I don’t know how many times we need to break out the idiot club, but date, time and timezones are extremely complicated - unless your business is primarily concerned with them you must use a library or service.

    Do Not Reinvent This Wheel

    • jsomae@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      7 months ago

      What does tz_database do? Wikipedia makes it seem like it basically converts a pair (geocoordinatr, utc time) to local time