• lysdexic@programming.devOP
      link
      fedilink
      English
      arrow-up
      9
      ·
      11 months ago

      I’d love to see benchmarks testing the two, and out of curiosity also including compressed JSON docs to take into account the impact of payload volume.

      Nevertheless, I think there are two major features that differentiate protobuff and fleece, which are:

      • fleece is implemented as an appendable data structure, which might open the door to some usages,
      • protobuf supports more data types than the ones supported by JSON, which may be a good or bad thing depending on the perspective.

      In the end, if the world survived with XML for so long, I’d guess we can live with minor gains just as easily.

      • aes@programming.dev
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        11 months ago

        “Appendable” seems like a positive spin on the “truncated YAML-file is frighteningly often valid” problem…

        • lysdexic@programming.devOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          11 months ago

          "Appendable” seems like a positive spin on the (…)

          I don’t think your take makes sense. It’s a write-only data structure which supports incremental changes. By design it tracks state and versioning. You can squash it if you’d like but others might see value in it.

    • lemmyvore@feddit.nl
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      11 months ago

      It’s not serialized from what I understand so it doesn’t need parsing. It’s sort of a structure+pointer dump. We’ll see how well that translates to other languages than C though.