• 0 Posts
  • 18 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle




  • Years

    YYYY

    ±YYYYY

    ISO 8601 prescribes, as a minimum, a four-digit year [YYYY] to avoid the year 2000 problem. It therefore represents years from 0000 to 9999, year 0000 being equal to 1 BC and all others AD, similar to astronomical year numbering. However, years before 1583 (the first full year following the introduction of the Gregorian calendar) are not automatically allowed by the standard. Instead, the standard states that “values in the range [0000] through [1582] shall only be used by mutual agreement of the partners in information interchange”.[20]

    To represent years before 0000 or after 9999, the standard also permits the expansion of the year representation but only by prior agreement between the sender and the receiver.[21] An expanded year representation [±YYYYY] must have an agreed-upon number of extra year digits beyond the four-digit minimum, and it must be prefixed with a + or − sign[22] instead of the more common AD/BC (or CE/BCE) notation; by convention 1 BC is labelled +0000, 2 BC is labeled −0001, and so on.[23]

    If you’re being handed a string 2022424-12-19T14:44:39Z, and told it’s ISO-8601, you should be able to figure it out. Really, a decent parser should be able to recognize that on its own (just use {4,} instead of {4} in regex). It does mean that non-hyphenated YYYYMMDD shouldn’t be used (I typically never see them encoded that way) - but even if you did, you’d just do (\d{4,})(\d{2})(\d(2}).


  • dx1@lemmy.worldtomemes@lemmy.worldWe're being short-sighted
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    edit-2
    8 days ago

    Planes crashing out of the sky wouldn’t have been inconceivable. Say you have two air traffic control systems that are synchronizing - one handles dates with a modulo 100 (00-99, i.e. 1900-1999), another handles them in epoch time. All of a sudden the two reported time + positions of two different planes don’t match up by a century, and collision projection software doesn’t work right. I’ve seen nastier bugs than that, in terms of conceptual failure.

    At no point is that a theory about a “conspiracy” either, IDK why you’re bandying that term around.



  • dx1@lemmy.worldtoMemes@lemmy.mlI'm too high for this
    link
    fedilink
    arrow-up
    9
    arrow-down
    19
    ·
    edit-2
    1 year ago

    Big ol eye roll.

    Not about wimpiness or grimacing at the picture. More about gradually recognizing that you’re just eating pieces of animal flesh. For me, that went hand in hand with studying biology & med textbooks, about a decade ago. Not irrational, I’m not going “it’s icky”, it’s me knowing what the chemical composition is, where it came from, what it is, and going, “yeah this is fucking nasty”.



  • dx1@lemmy.worldtoMemes@lemmy.ml***
    link
    fedilink
    arrow-up
    7
    ·
    1 year ago

    That’s a way taller order than you might think. Docker has loads of kernel level integration that FreeBSD isn’t interested in supporting, also there are separate techs for similar purposes, like jails.










  • dx1@lemmy.worldtoMemes@lemmy.mlI like a good UX
    link
    fedilink
    arrow-up
    5
    arrow-down
    2
    ·
    edit-2
    1 year ago

    And then

    1. Network effects matter, supporting open source software promotes its adoption and lowers barriers to entry for technological literacy and accessibility, accelerating the technological and social development of humanity

    Although that doesn’t have the same ring as “fuck these dumb cult members because i don’t care and they shouldn’t either”.