Meme transcription:

Panel 1: Bilbo Baggins ponders, “After all… why should I care about the difference between int and String?

Panel 2: Bilbo Baggins is revealed to be an API developer. He continues, “JSON is always String, anyways…”

  • ShortFuse@lemmy.world
    7·
    5 months ago

    The meme format is awesome, but JSON differentiates strings with ".

    { "key": 1337 } vs { "key": "1337" }.

    You might be thinking yaml? (Though it supports ' and " for explicit string types, technically)

    But integer vs float? Good luck.

    • ApexHunter@lemmy.ml
      11·
      5 months ago

      The joke is that, regardless of how the type is declared in json, you are parsing a string. (your json blob is just a series of characters, not raw binary data)

      • Zucca@sopuli.xyz
        3·
        5 months ago

        Yes. And many people here doesn’t seem to get that.

        I’m not a dev of any kind. I occasionally write some bash and awk scriots to automate some things and if I need some kind of plain text (non-binary) data format I prefer tsv over json.

        So why do I still get this? Is it just that many json advocates want to make sure others know json does support other data types than plain string?