• @FilthyShrooms
    link
    484 months ago

    That’s why my business only uses pure, crisp .txt files. If I can’t open it in notepad, I don’t want it!

    • @[email protected]
      link
      fedilink
      264 months ago

      I have unironically been preaching the powers of text and JSON, and have some converts. Universal compatibility is great.

      • @[email protected]
        link
        fedilink
        English
        34 months ago

        Json is a garbage format for anything that’s meant to ever be touched by a human. At least use yaml or json5.

        • @[email protected]
          link
          fedilink
          3
          edit-2
          4 months ago

          In the first paragraph of JSON5’s site:

          It is not intended to be used for machine-to-machine communication.

          YAML is not supported by a lot of enterprise software (example: Azure pipelines supports it but Power Automate does not). JSON, XML, CSV, or failing that Text are the safe bets. We use a few options for reading or building presentation layers quickly. Ultimately the idea is to move data around in a way that is friendly to our current and future applications.

          • @[email protected]
            link
            fedilink
            English
            24 months ago

            It’s absolutely trivial to convert either format to json if necessary. The real killer for me with json is the lack of comments. Human-maintained files absolutely need comments.