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…”

    • lad@programming.dev
      1·
      5 days ago

      I disagree a bit in that the schema often doesn’t specify limits and operates in JSON standard’s terms, it will say that you should get/send a number, but will not usually say at what point will it break.

      This is the opposite of what C language does, being so specific that it is not even turing complete (in a theoretical sense, it is practically)

      • JackbyDev@programming.devEnglish
        2·
        5 days ago

        Then the problem is the schema being under specified. Take the classic pet store example. It says that the I’d is int64. https://petstore3.swagger.io/#/store/placeOrder

        If some API is so underspecified that it just says “number” then I’d say the schema is wrong. If your JSON parser has no way of passing numbers as arbitrary length number types (like BigDecimal in Java) then that’s a problem with your parser.

        I don’t think the truly truly extreme edge case of things like C not technically being able to simulate a truly infinite tape in a Turing machine is the sort of thing we need to worry about. I’m sure if the JSON object you’re parsing is some astronomically large series of nested objects that specifications might begin to fall apart too (things like the maximum amount of memory any specific processor can have being a finite amount), but that doesn’t mean the format is wrong.

        And simply choosing to “use string instead” won’t solve any of these crazy hypotheticals.

        • lad@programming.devEnglish
          1·
          5 days ago

          Underspecified schema is indeed a problem, but I find it too common to just shrug it off

          Also, you’re very right that just using strings will not improve the situation 🤝