#Meme #Humour
-
DD/MM/YYYY of all possible options!??
Because we'll immediately confuse it with the American MM/DD/YYYY?
-
@benroyce @cmconseils 86 47 by all means, but you also gotta 8601.
#iso8601ftw -
@ramsey @cmconseils @benroyce fully agree
-
This date format is used here in India. Why does the USA has some complex date format?
because AMERICA NUMBER ONE WOOOH or some other stupid shit
-
@cmconseils
Big-endian? WTF. I thought the human way to write scalars was little-endian.
Faux stardate is the absolute best:2026.0715 or
2026.0715.1002
with timestamp. (Yes this breaks the ability of faux stardate with only a date to be stored as a plain float when convenient.) Add seconds dot decimal parts of second as needed, along with zulu hour offset as desired.
2026.0715.1002.45.3142.z-5It's so concise and easy to read that adding the day of the week looks pretty good with it.
2026.0715 Wednesday -
-
@cmconseils I personally prefer the ISO YYYY-MM-DD format.
-
@ramsey @cmconseils @benroyce Not all women like big endians. That's just a myth.
-
@cmconseils run away from this man. He’s pretending to hate on MM/DD/YYYY and getting it very wrong.
It’s like the Terminator 2 “your foster parents are dead” bit.
-
@ramsey @cmconseils @benroyce Not all women like big endians. That's just a myth.
-
@cmconseils Got it:
8128-06-28Three perfect numbers in the perfect date format.
Too bad we'll have to wait a long time for that...
-
@zalasur
But not ISO.Use YYYY-MM-DD instead, because / are confusing and not possible in file names on several operating systems.
@beandev @zalasur @DXMacGuffin @cmconseils behold: https://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc32300.1570/html/sqlug/BABDBAHF.htm
yes YY not this newfangled YYYY
-
Oh @cmconseils you've done it now. You've aroused the nerds!
(By the way, ISO 8601 will no longer lexically-sort properly once the year 10000 comes.)
-
@cmconseils I'm pretty alright with every date format. Same with 12 and 24 hour since I was a kid
I just use MM/DD/YY or MM/DD/YYYY cos a ton of people I interact with on the net are americans, but I like YYYY-MM-DD
-
@cmconseils EW! DUMP HIM! YYYY-MM-DD is most efficient both to read and sort.
-
Oh @cmconseils you've done it now. You've aroused the nerds!
(By the way, ISO 8601 will no longer lexically-sort properly once the year 10000 comes.)
@argv_minus_one @cmconseils @ckd @beandev @zalasur @DXMacGuffin Now THAT is job security!
-
@zalasur
But not ISO.Use YYYY-MM-DD instead, because / are confusing and not possible in file names on several operating systems.
@beandev @zalasur @DXMacGuffin @cmconseils This is the way.
-
@cmconseils
Big-endian? WTF. I thought the human way to write scalars was little-endian.
Faux stardate is the absolute best:2026.0715 or
2026.0715.1002
with timestamp. (Yes this breaks the ability of faux stardate with only a date to be stored as a plain float when convenient.) Add seconds dot decimal parts of second as needed, along with zulu hour offset as desired.
2026.0715.1002.45.3142.z-5It's so concise and easy to read that adding the day of the week looks pretty good with it.
2026.0715 Wednesday@RustedComputing @cmconseils Still assumes month-and-day ordering. Better to use Julian day-of-year for star date format: 2026.196.
-
@argv_minus_one @cmconseils @ckd @beandev @zalasur @DXMacGuffin Now THAT is job security!
@obscurestar @argv_minus_one @cmconseils @ckd @beandev @DXMacGuffin Yep I'm looking forward to when the Y10K problem becomes a serious concern. And in all likelihood COBAL will still be around that will need to be fixed. Again.
-
@obscurestar @argv_minus_one @cmconseils @ckd @beandev @DXMacGuffin Yep I'm looking forward to when the Y10K problem becomes a serious concern. And in all likelihood COBAL will still be around that will need to be fixed. Again.
@zalasur @obscurestar @argv_minus_one @cmconseils @ckd @beandev
Call me short sighted, but I will not be changing my career plans because of the Y10K problem.
