Hacker News Reader

Comment by phist_mcgee | Hacker News Reader

I think that's a solution looking for a problem.

Payment via bank transfer is also a contract, the dispute resolution is no different. I don't see how a promise note on a piece of paper somehow protects you better than an electronic transfer that is visible to you, the other party, the bank, and to authorities.

View on HN

Agree. It's like Stockholm Syndrome. It comes across the same as when someone from the US tries to argue that putting the month before the day actually makes sense in dates because then the max values go from lowest to highest (12/31/9999+).

That is the perfect moment to mention ISO 8601 and RFC 3339.

I started using 8601 without even thinking about it for one simple reason. Alphabetical sorting just works with YYYYmmdd

So for example, log20220804.txt

https://xkcd.com/1179/

At the very least, use four digit years, not 22 for 2022.

> ISO 8601 was published on 06/05/88 and most recently amended on 12/01/04.

I've been using that format too for the same reason, without knowing about 8601. Day/Month/Year is great for a person (I'm in Aus) since we, as human beings, intrinsically know what year it is, and probably know what month it is if we haven't been on a bender. But string sorting is so much easier using yyyyMMdd format.

yyyymmdd is incorrect, as pointed out explicitly in the xkcd you linked.

The format is yyyy-mm-dd.

US and non-US date styles are equally wrong. It’s just personal preference or what you are used to. The only “correct” option would be Year Month Day, and the only argument that needs to be made for is look at how your clock arranges time, or how you write it down.

Reply on news.ycombinator.com