Re: [Patch] Update 24-hour times to use two digits for the hour

[Eric Wong <e@yhbt.net>]

Varun Varada <varuncvarada@gmail.com> wrote:
> Hi Eric,
> 
> The "why?" is that leading zeroes are standard for virtually any
> 24-hour clock in the world
> (https://www.google.com/search?q=24-hour+time). This is even codified
> in the ISO 8601 standard
> (https://en.wikipedia.org/wiki/ISO_8601#Times), which the project
> seems to be following. Without a leading zero, a user immediately
> expects an a.m./p.m. modifier, which there is not.

Sorry, but no.  This project does NOT blindly follow ISO-8601 or
such standards when it comes to output intended for humans.

I admit the lack of AM/PM could be confusing at first in
standalone cases; but someone needs to learn that exactly once.

What I care more about is repeated tasks.  Making users focus
their eyes and waste energy parsing date and times for every
single thread they look at is much worse than training them
for one thing.

Take for example:
https://public-inbox.org/git/20200222201749.937983-1-sandals@crustytoothpaste.net/T/#t

2020-02-24 18:26   ` Junio C Hamano
2020-02-25 10:29   ` Johannes Schindelin
2020-02-25 19:25     ` Junio C Hamano
2020-02-26  3:05       ` brian m. carlson
2020-02-26  3:11         ` Junio C Hamano
2020-02-26  2:23     ` brian m. carlson
2020-02-27 13:24       ` Johannes Schindelin
2020-02-27 15:06         ` Junio C Hamano

With the leading space instead of zero, my eyes don't even need
to be in focus to know the replies from 2-26 were on a different
day than the rest.  The shape of the text is enough to tell,
I don't have to bring my eyes into focus to know that.