Live data from Hacker News

Freedom Clock

domsson.github.io

1–10 of 189 posts

Re: Freedom Clock

#2
Should we list hours, minutes, seconds? or year, month, day? Should we drive on the right side of the road or left? Should we use imperial or metric system? These are all good questions but I think the answer is "it depends." Just like timezones. You can't get rid of timezones: https://news.ycombinator.com/item?id=26416337

https://qntm.org/abolish

Re: Freedom Clock

#3
I get it, it's really annoying that there are different formats.

In fact I once nerfed a small database by importing a bunch dates from a csv in the wrong format.

But honestly both formats (M/D/Y and D/M/Y) are wrong, as clear from the clock example: dates should be big-endian; Y/M/D.

Re: Freedom Clock

#5
post #3

I get it, it's really annoying that there are different formats. In fact I once nerfed a small database by importing a bunch dates from a csv in the wrong format. But honestly both formats (M/D/Y and D/M/Y) are wrong, as clear from the clock example: dates should be big-endian; Y/M/D.

Iso8601 for the win!

Re: Freedom Clock

#6
The monkey’s paw curls, and Americans adopt this time format as well just to spite the rest of the world for complaining about their preferred date format.

Re: Freedom Clock

#8
post #3

I get it, it's really annoying that there are different formats. In fact I once nerfed a small database by importing a bunch dates from a csv in the wrong format. But honestly both formats (M/D/Y and D/M/Y) are wrong, as clear from the clock example: dates should be big-endian; Y/M/D.

While I agree that big-endian dates are the best solution (if nothing else, because lexical sort puts it in the right order), I think little-endian at least makes sense. The middle-endian format is just absurd.
Post reply on HN