image saying "at least the important software isn't being vibe cod-" (cut off) and showing a graph of em dashes in the linux kernel over time with a sharp rise the past few years
you are viewing a single comment's thread
view the rest of the comments
[–] 58 points 2 weeks ago (25 children)

You can get a lot done when you've got 29 months in a year

  • source
  • hideshow 25 child comments
  • [–] 3 points 2 weeks ago (23 children)
  • [–] 33 points 2 weeks ago (3 children)

    The weird US American Date scheme is not used in most of the world.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 5 points 2 weeks ago (2 children)

    I wish. Am European. I know one person that voluntarily uses their date and time formats. For reasons I will never comprehend.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 2 weeks ago (1 child)

    He or she must enjoy the endless confusion and friction in the interaction with others. That said, some idiotic IT systems use the US format to. Causes a lot of problems.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 2 weeks ago*

    I'm in the US and have had problems with C-level douches misreading dd-mm-yyyy dates in some system we had that logged in that format and freaking out (and also missing that the log time stamps were in UTC-0, causing further confusion/freakout)

    Anyway, this is part of why I always use yyyy-mm-dd, because nobody will confuse that date string for any other date, and everyone who can understand dates at all will be able to read it.

  • source
  • parent
  • [–] 25 points 2 weeks ago (15 children)
  • [–] 24 points 2 weeks ago (2 children)
  • [–] 13 points 2 weeks ago (11 children)

    Because one lives the other should not long live Y-M-D

  • source
  • parent
  • hideshow 11 child comments
  • [–] 19 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

    NO. You need a character per digit and you always want the leading 0 shown.

    YYYY-MM-DD

  • source
  • parent
  • hideshow 2 child comments
  • [–] 19 points 2 weeks ago (1 child)

    ISO 8601 is the only correct way.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 2 weeks ago

    It's close, sure, but actually no. That standard currently requires the letter T (and no white-space) between date and time when both are present, and, frankly, that's ugly and a space should be allowed.

    An old version of the standard allowed the space, and GNU's coreutils seem to have carried on the tradition, so I'm not alone in thinking this.

  • source
  • parent
  • [–] 1 point 2 weeks ago (5 children)

    OP's graph uses slashes.

    Dashes would remove all the confusion.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 6 points 2 weeks ago* (4 children)

    No because it's the global format that typically uses periods.

    D.M.Y (normal)
    Y-M-D (superior)
    M/D/Y (mental illness)

    Mixing up the formats and denominators makes this mess even worse.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 2 weeks ago (3 children)

    you should also always specify YYYY-MM-DD because often M and D ignores leading zeros, YY means the 2 digit suffix, and Y… well, i don’t even know what that is but i’m sure it’s something less specific than YYYY

    if we’re going to be picky about being clear about things, let’s be truly clear about things

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 2 weeks ago (1 child)

    YYYYY would be something like "The Year of Our Lord, Two-Thousand and Twenty-Six" (or probably just "Twenty Twenty-Six", but the other is more ridiculous so I'll go with that)

    Y would just be "6" but I can't think of any context where that would ever be used

  • source
  • parent
  • hideshow 1 child comment