News for hackers. Stuff that matters.
Re:Show HN: JSON-based standard for job posts by tokenizerrr on Monday January 19, 2015 @08:33AM (#8911825)
What is your problem with this? This is how dates are communicated in large swaths of the world (dd-mm-yyyy), including my home country. Sure, it would be better to use ISO8601 in a standard like this, but you don't see non-Americans responding with "seriously?" when an American uses "mm/dd/yyyy" (which happens a lot).

Perhaps try to be a little more open minded, and if you do decide to deliver criticism then perhaps do so in a constructive manner, instead of "seriously?".

Re:Show HN: JSON-based standard for job posts by PeterWhittaker on Monday January 19, 2015 @08:42AM (#8911858)
As a non-American, seriously was close to one of my first thoughts too. Then again, I think when my fellow Canadians use that format - it's inherently ambiguous, and most likely to be understood only/mostly by Americans.

(We're more likely to use dd/mm/yy, but that's still ambiguous, and is most likely to confuse Americans.... I always use yy/mm/dd in the completely unvalidated and taken on faith belief that it will be clear. YMMV, etc.)

Re:Show HN: JSON-based standard for job posts by tokenizerrr on Monday January 19, 2015 @08:50AM (#8911890)
Right, this should have been ISO8601 to remove any ambiguity. I just think it's surprising and offensive that:

1) People consider the American format to be the one and only legitimate format, and everything else is met with resistance 2) I am getting downvoted for stating this

It wouldn't surprise me if the OP is not an American, and they simply used the format native to them. Do we really consider this enough reason to start ridiculing it?

Re:Show HN: JSON-based standard for job posts by omeid2 on Monday January 19, 2015 @08:39AM (#8911847)
Not only this is common all around the world but it is also "ordered" correctly. dd/mm/yyyy (smallest, middle, largest) makes a lot more sense than mm/dd/yyyy (middle, smallest, largest).
Re:Show HN: JSON-based standard for job posts by bobmagoo on Monday January 19, 2015 @11:28AM (#8912565)
It really doesn't though.

Think about the sorting use case: Say you've got a bunch of files on your system with the date as the first part of the filename, what is more meaningful, sorting by year (2015-01-19_file), or by the date (19-01-2015_file). Clearly, sorting by year the files were created is more meaningful than sorting by the day of the month the files were created.

Edit: I completely misread your comment as saying that smallest to largest is more useful than largest to smallest, rather than the weird month-day-year thing we use in America. Completely agree an ordering by specificity is more useful, but going from least to most specificity makes it much easier to order things in a useful way.

Re:Show HN: JSON-based standard for job posts by onion2k on Monday January 19, 2015 @08:48AM (#8911881)
Note the example didn't use dd/mm/yyyy. It used dd-mm-yyyy. Generally you can assume that a dash delimited date will be in European format while a slash delimited date will be American. The problems arise when British (and former British colonies) are added to the mix, because we use the European format with slashes.

The only truly unambiguous format is yyyymmdd.

Re:Show HN: JSON-based standard for job posts by lukasm on Monday January 19, 2015 @09:09AM (#8911943)
Not sure how yyyymmdd is unambiguous. 10111012 do you mean 10th Nov 1012 or 1011 Oct 12th
Re:Show HN: JSON-based standard for job posts by onion2k on Monday January 19, 2015 @09:26AM (#8912014)
How old are the people using this CV format?! For any date that would appear on in someone's work history yyyymmdd is not ambiguous, but if you're being really strict then a delimiter would fix the problem.
Re:Show HN: JSON-based standard for job posts by nsgi on Monday January 19, 2015 @11:35AM (#8912608)
yyyy/mm/dd is ordered even more correctly. With dd/mm/yyyy the most significant digit is the 5th of eight and the least is the 2nd.
Re:Show HN: JSON-based standard for job posts by nsgi on Monday January 19, 2015 @11:37AM (#8912619)
Do they use it in protocols?