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

    • themusicman@lemmy.world
      4·
      4 months ago

      If you’re moving away from text formats, might as well use a proper serialisation tool like protobuf…

    • bleistift2@sopuli.xyzOPEnglish
      3·
      4 months ago

      Hell, no. If I wanted to save bytes, I’d use a binary format, or just fucking zip the JSON. Looking at a request-response pair and quickly understanding the transferred data is invaluable.

        • wtfrank@feddit.ukEnglish
          1·
          4 months ago

          Fine, and if you don’t use json in your API because of the deficiency highlighted in the meme, what format do you use in your API?

          • JackbyDev@programming.devEnglish
            1·
            4 months ago

            I use JSON. I have used Avro for things in Kafka but I’m not sure the benefits outweigh the negatives. Avro is much more complicated than people think and most folks don’t really have a strong desire to learn how it should be used and do stuff incorrectly. Everybody knows JSON and it works with everything though. (Example: so many people just hear that Avro schemas can be backwards compatible but have zero idea that you still need the schema that wrote the message even if you want to read it into a newer one.)

            Interestingly, I take the meme as saying a dev is using the wrong types in their serialization format (using strings to store integers) which was my biggest problem with Avro. Mostly from people not using logical types or preferring to use ISO 8601 datetime strings instead of the built-in timestamp-millis type.