1929
2023-08-09.jpg (lemmy.ml)
submitted 3 years ago* by to c/memes@lemmy.ml
321 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 16 points 3 years ago* (7 children)

The 3 "M"s are not numerical, but indicate characters. For example 01 Jan 2023.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 4 points 3 years ago (4 children)

    Considering how there's almost no computers anymore with such limited resources that they can't store a string or convert to one, it's kind of crazy anybody bothers with the ambiguity of using numbers for the month.

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

    The limited resource is not Compute Power, but Engineer time. Sure, you could ask someone to implement wrappers everywhere in the system so that the display is human-readable - or you could put one label somewhere clarifying the date format to readers.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 3 years ago (1 child)

    Implement wrappers everywhere? Why can't they just write a single function that takes an ISO date a spits out a string (human readable) date? I'd put money down that such a function already exists in almost every library that deals with dates.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 3 years ago

    That's why I said "implement" and not just "write". The process of wiring in that existing function has non-negligible cost, as does keeping it updated/patched.

    Sure, it should be pretty small - but it's non-zero. Is it worth it? That's a product decision.

  • permalink
  • fedilink
  • source
  • parent