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

YYYY-MM-DD HH:II:SS

It’s sortable, it’s usable, and you can’t get it wrong unless you really try.

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

DD/MM/YY HH:II:SS

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.

Remove timezones. Everywhere UTC. It would make life so much easier

And also: remove daylight saving time.

@stisch i vote for binary unix epoch watches

ISO8601

DD.MM.YYYY HH:II:SS

@host127001
I'd prefer Hex l. It's shorter

Unix time