• Semperverus@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    3
    ·
    1 month ago

    I wish we would all start switching over to JSON for configuration files. It’s so much easier to parse, and you can’t screw it up with too many spaces or not enough.

      • tiramichu@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        1 month ago

        My biggest peeve with JSON when I’m forced to use it as a configuration format is that it doesn’t have any syntactical support for comments.

        So I can’t even add any notes to the file.

        • lightnegative@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 month ago

          Yep this for me too. Thankfully VSCode allows comments in its settings.json / launch.json files but most programs use strict JSON which doesn’t allow comments

      • Voroxpete@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 month ago

        Yeah, this is my biggest annoyance with JSON. As a data structure it’s very elegant, but it only really makes sense to people who know how to code, and without the ability to add comments you have to rely heavily on external documentation to make it readable to most users.

    • Voroxpete@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      1
      ·
      1 month ago

      Instead you can screw it up by having too many commas or not enough. Hardly that much of an improvement.

    • lightnegative@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 month ago

      I used to think that until I figured out yaml and now yaml isn’t so bad.

      It helps that text editors know what yaml is now so insert spaces when you hit tab etc