I feel that Yaml sucks. I understand the need for such markup language but I think it sucks. Somehow it’s clunky to use. Can you explain why?

  • Windex007@lemmy.world
    link
    fedilink
    arrow-up
    104
    arrow-down
    25
    ·
    3 months ago

    Any language in which whitespace has syntactic value is intrinsically flawed.

    Can’t speak to your specific issues, but that’s why yaml will always suck.

    • deegeese@sopuli.xyz
      link
      fedilink
      arrow-up
      29
      arrow-down
      6
      ·
      3 months ago

      As a serialization format, agree 100%, but would Python really be better if it switched to braces?

      • magic_lobster_party@fedia.io
        link
        fedilink
        arrow-up
        60
        arrow-down
        4
        ·
        3 months ago

        Yes, I think so. The downside with Python comes when refactoring the code. There’s always this double checking if the code is correctly indented after the refactor. Sometimes small mistakes creep in.

        It’s really hard to tell when Python code is incorrectly indented. It’s often still valid Python code, but you can’t tell if it’s wrong unless you know the intention of the code.

        In order languages it’s always obvious when code is incorrectly indented. There’s no ambiguity.

        • GBU_28@lemm.ee
          link
          fedilink
          English
          arrow-up
          14
          arrow-down
          3
          ·
          3 months ago

          I think this is just familiarity. I never have issues with indentation, but when refactoring js I’m always like hey who’s fucking brace is this

        • deegeese@sopuli.xyz
          link
          fedilink
          arrow-up
          19
          arrow-down
          16
          ·
          3 months ago

          It’s only hard to tell indentation in Python when the code block gets longer than about a screen, which is usually a sign the code should be refactored into smaller methods.

          • hex@programming.dev
            link
            fedilink
            arrow-up
            2
            ·
            3 months ago

            People hate hearing that they are bad coders 😂

            You and the other guy are saying to focus on writing code with less indentation and using smaller methods, and you both got downvoted.

            I fully agree, small methods all the way, and when that’s not possible it’s time to refactor into possibility!

          • gravitas_deficiency@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            2
            arrow-down
            1
            ·
            3 months ago

            As someone who has been working in Python a ton for the last couple years, it’s amusing to me how many downvotes you’re getting for simply noting that good code style and tight, terse, modularized implementation of business logic more or less addresses the issue. Because it absolutely does in the vast majority of cases.

        • Kache@lemm.ee
          link
          fedilink
          arrow-up
          6
          arrow-down
          6
          ·
          edit-2
          3 months ago

          Can address it by writing code that doesn’t depend much on indentation, which also makes code more linear and easier to follow.

          • poinck@lemm.ee
            link
            fedilink
            arrow-up
            1
            ·
            3 months ago

            Yes, totally agree, and it applies to formats and language syntaxes even if braces are used.

      • xmunk@sh.itjust.works
        link
        fedilink
        arrow-up
        33
        arrow-down
        8
        ·
        3 months ago

        Yes it would - look at optional braces for short if expressions in C family languages and why it’s so discouraged in large projects. Terminating characters are absolutely worth the cost of an extra LoC

        • deegeese@sopuli.xyz
          link
          fedilink
          arrow-up
          20
          arrow-down
          4
          ·
          3 months ago

          I started in C before moving on to C++, Java, Ruby and Python.

          I’ve had more bugs from missing braces than from misaligned whitespace because the latter is far more obvious when looking at a block of code.

        • Eager Eagle@lemmy.world
          link
          fedilink
          English
          arrow-up
          13
          arrow-down
          5
          ·
          edit-2
          3 months ago

          False dichotomy. Optional braces are bad practice because they mislead the programmer that is adding an additional clause to the block.

          This misleading behavior wouldn’t happen in Python, as it would either be invalid syntax, or it would be part of the block.

          Indentation problems are pretty obvious to the reader. Even more than missing or unbalanced braces.

          • xmunk@sh.itjust.works
            link
            fedilink
            arrow-up
            11
            arrow-down
            1
            ·
            3 months ago

            They may be obvious to the reader but they may be impossible to see if tabs and spaces are mixed together.

            Closing tokens are always clearer.

            • Eager Eagle@lemmy.world
              link
              fedilink
              English
              arrow-up
              6
              arrow-down
              3
              ·
              edit-2
              3 months ago

              yes, from my other comment

              the only mistake of Python when it comes to whitespaces was allowing hard tabs

              but that’s easily fixed with an editor setting - on the other hand, unbalancing braces (and not realizing it) is too easy all the time.

          • tyler@programming.dev
            link
            fedilink
            arrow-up
            1
            ·
            3 months ago

            That misleading behavior does happen in Python. The next programmer that comes along can’t tell if the original programmer fucked it up and didn’t unindent to put a statement outside of the block or if they meant to put it inside the block. I’ve debugged this one too many times and it takes hours each time because it’s impossible to see the bug at all!!

            • Eager Eagle@lemmy.world
              link
              fedilink
              English
              arrow-up
              2
              ·
              edit-2
              3 months ago

              The misleading behavior is about what you expect to execute in the source code you’re looking at vs what’s actually executed.

              What you describe is a logic ambiguity that can happen in any program / language.

              • tyler@programming.dev
                link
                fedilink
                arrow-up
                1
                ·
                2 months ago

                I don’t agree. It’s a direct result of whitespace, which does not happen if you don’t use whitespace. For example it can happen in Java and kotlin, but only if you use if statements without braces, which you pretty much never see. If you do see it you know to look out for the exact issue I described. That’s not possible in Python, since there is no alternative.

        • marcos@lemmy.world
          link
          fedilink
          arrow-up
          12
          arrow-down
          1
          ·
          3 months ago

          The end of line also has semantic meaning. Both indentation and eol are whitespace.

          • LainTrain@lemmy.dbzer0.com
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            3 months ago

            Indentation can be (and should be) tabs, EOL is it’s its own thing either \n or CRLF which Python source code did actually care about as recently as 2.3.

            Assumptions like this is why most people should stick to verbose languages with lots of guardrail braces.

    • Eager Eagle@lemmy.world
      link
      fedilink
      English
      arrow-up
      11
      arrow-down
      5
      ·
      edit-2
      3 months ago

      YAML sucks because, among other things, indenting it is not obvious.

      In contrast, the only mistake of Python when it comes to whitespaces was allowing hard tabs, which makes it too easy to mix them if your editor is not configured.

      Improper indentation stands out more than missing or unbalanced braces and it’s really not an issue to delimit code blocks.

    • marcos@lemmy.world
      link
      fedilink
      arrow-up
      9
      arrow-down
      3
      ·
      edit-2
      3 months ago

      Haskell supports both semantic whitespace and explicit delimiters, and somehow almost everybody that uses the language disagrees with you.

      But anyway, for all the problems of YAML, this one isn’t even relevant enough to point out. Even if you agree it’s a problem. (And I agree that the YAML semantic whitespace is horrible.) If YAML was a much better language, it would be worth arguing whether semantic whitespace breaks it or not.

    • AdamBomb@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      2
      ·
      3 months ago

      Not any language. I code professionally in F# which has semantic whitespace and it has literally never been an issue for me or my team. In contrast to Python, it’s a compiled language and the compiler is quite strict, so that probably helps.

    • Nighed@sffa.community
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 months ago

      It’s the only time that tabs Vs spaces really riles me up. So annoying when everyone has different tab lengths

    • Ben Matthews@sopuli.xyz
      link
      fedilink
      Português
      arrow-up
      2
      arrow-down
      2
      ·
      3 months ago

      I now use Scala 3, and very happy with syntactic whitespace (combined with an intelligent compiler)