11

If you had the power to enforce a datetime format globally, which one would you choose?

Comments
  • 9
    YYYY-MM-DD HH:II:SS

    It’s sortable, it’s usable, and you can’t get it wrong unless you really try.
  • 2
    I wouldn't want to enforce a universal datetime format because there can be many different requirements in different scenarios that cannot be satisfied in one single format.
    For example:
    -has to be short
    -has to include the timezone
    -has to include day of week
    -has to account for hours that exist twice because of daylight saving time
    -has to satisfy regional conventions
    -has to be sortable
    -has to include the name of the month
    And so on
  • 4
    DD/MM/YY HH:II:SS
  • 7
    UNIX EPOCH TIMESTAMPS, GMT.

    Everyone can wear big-ass red LCD watches that are 15 characters long, how cool would that be? Plus no more time zone / daylight savings nonsense.
  • 2
    Remove timezones. Everywhere UTC. It would make life so much easier
  • 3
    And also: remove daylight saving time.
  • 2
    @stisch i vote for binary unix epoch watches
  • 2
    ISO8601
  • 2
    DD.MM.YYYY HH:II:SS
  • 1
    @host127001
    I'd prefer Hex l. It's shorter
  • 0
    Unix time
Add Comment