Earlier quoted context omitted.
0°F: cold, 100°F: warm 0°C: cold, 100°C: dead 0 K: dead, 100 K: dead
There is no degree symbol in Kelvin.
Thanks, updated.
Freedom Clock
161–170 of 189 posts
Re: Freedom Clock
#162Where's the European clock with the seconds first?
Exactly! What date format was used to land on the moon?
MET: Mission Elapsed Time, HH:MM:SS, from liftoff. https://www.hq.nasa.gov/alsj/a11/a11.step.html @ 109:24:23
Re: Freedom Clock
#163Earlier quoted context omitted.
America’s insistence on weird date and unit formats has a negative effect on software and resources used all around the world.
Developers aren't using M/D/Y. This is a straw man.
Developers and their APIs might not be. The user-facing software often does, and it often does not let you switch, at least not without affecting other things (such as the spelling of “colour”).
Re: Freedom Clock
#164Earlier quoted context omitted.
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.
Yes, but the confusion caused by not knowing which way your writing it makes both ways worthless (unless your audience is strictly IN or OUT of the US - OR - if one number is greater than 12). It's annoying, and I just ALWAYS use YYYY-MM-DD, and everyone is happy. Please join my cause. If there's one thing we can all agree makes the world just a little better, it's using YYYY-MM-DD to get people used to it.
I do the same.
Re: Freedom Clock
#165I 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.
I'd much rather have D/M/Y, since then data is ordered by relevance. If I'm seeing a full date, I probably care more about the day than the month, and more about the month than the year. This is just pure bikeshedding tho, both are infinitely better than M/D/Y
Relevance changes by which time scale you're looking at. If you're looking at the last month, the day is most important. If you're looking at last year, month is probably most important. And for anything beyond a year, year is obviously most important.
Re: Freedom Clock
#166Earlier quoted context omitted.
Yeah, I don't think so. If it's 0°C outside, I know it's probably time to put winter tires on because the water in the puddles will freeze. If water in the pot on my stove is close to 100°C, I know it will boil soon. Same with dates — it has nothing to do with being machine readable or not, dates should go from largest to smallest (yyyy-mm-dd, etc) or vise versa, not turn 180 degrees at midpoint for some reason. Your…
0°F: cold, 100°F: warm 0°C: cold, 100°C: dead 0 K: dead, 100 K: dead
300 K: about ideal
> 300 K: hot
Let's switch to Kelvins
Re: Freedom Clock
#167Earlier quoted context omitted.
> Here we are on March 25. The year comes last because it's least important. Sorry to break it to you, but in the UK, Australia or India you wouldn't say March 25, you would say 25 March or 25th March. Just as you would in Spanish, French or German. The fact that you say March 25 reflects the atypical American date standard. They do say March 25 in Chinese, but that's because they use YMD order (and when saying a ful…
As a weird contradiction, don't Americans also generally say '4th of July' when referring to the holiday?
A relic of being a colony.
Re: Freedom Clock
#168Re: Freedom Clock
#169I 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!
I am kinda shocked no one has posted this yet: https://xkcd.com/1179/
Re: Freedom Clock
#170I 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.
Yeah.. the hungarians are F-ed as usual: https://en.wikipedia.org/wiki/Date_and_time_notation_in_Hung...