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?

  • Vivendi@lemmy.zip
    link
    fedilink
    arrow-up
    82
    arrow-down
    19
    ·
    edit-2
    2 months ago

    Can people stop hating on shit?

    FOR FUCKS SAKE, negative reinforcement dopamine has RUINED THE FUCKING NET.

    EVERYWHERE I GO there’s someone bitching about something, hate circlejerks are unbelievably popular, people just love to hate on stuff.

    You’re ruining your thought patterns with all these social media negativity bullshit.

    Fucking TOML users hate on fucking YAML fucking C++ users hate Rust fucking Rust users hate literally everything under the sun and are insufferable to work with

    EVERYONE, fucking CHILL

    • Sir Gareth@programming.dev
      link
      fedilink
      arrow-up
      11
      ·
      2 months ago

      Yeah TBH I like yaml. Sure its not the best ever, but its not the worst it could possibly be.

      For config its not terrible. For ansible playbooks its again… not terrible.

      Why is everyone always hating on something which is just kinda mid.

      • SandLight@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        2 months ago

        I dream of a life where I use YAML but all my configs are stuck in XML. People can complain but there’s always worse options.

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

          One nice thing about XML is that there’s an official way to link to the schema from within the document. If you do that you can easily automatically validate it, and even better you get fantastic IDE support via Red Hat’s LSP server. Live validation, hover for keys, etc.

          It’s a really nice experience and JSON schema can’t really match it.

          That said, XML just has the wrong data model for 99% of use cases.

      • wewbull@feddit.uk
        link
        fedilink
        English
        arrow-up
        8
        ·
        2 months ago

        Config is fine, but Yamls biggest problem is people use it to describe programs. For example: playbooks. For example: CI steps.

        If YAML wasn’t abused in this way it would have a lot less hate.

        • derpgon@programming.dev
          link
          fedilink
          arrow-up
          4
          ·
          2 months ago

          What’s wrong with using YAML for CI? I mean, I use it for Gitlab CI, the underlying script it runs is just Bash.

          • wewbull@feddit.uk
            link
            fedilink
            English
            arrow-up
            4
            ·
            2 months ago

            Right, so you just have a single step and then hand over to a proper script. I’ve seen many people try to put much more complex logic in there before handing over to a proper language.

          • cashew@lemmy.world
            link
            fedilink
            arrow-up
            4
            ·
            2 months ago

            You’re doing it right by avoiding as much of Gitlab’s CI features. I’ve seen versions where scripts are inlined in the YAML with expressions in random rule fields and pipeline variables thrown all over the place. And don’t get me started on their “includes” keyword, it’s awful in practice, gives me nightmares.

            Then I write a Kubernetes manifest in YAML with JSON schema validation and the heart rate goes down again.

    • orcrist@lemm.ee
      link
      fedilink
      arrow-up
      6
      ·
      2 months ago

      No seeds no stems no stress my guy. The Internet is a great place for complaining. Readers can downvote and move on, everyone gets what they want.

  • ulkesh@beehaw.org
    link
    fedilink
    English
    arrow-up
    5
    ·
    2 months ago

    White space/indentation as a construct of the syntax.

    It’s why I have a hard time with python.

    People have their likes and dislikes. Nothing wrong with that.

  • ITGuyLevi@programming.dev
    link
    fedilink
    arrow-up
    13
    ·
    2 months ago

    I hated yaml with every fiber of my being when first had to use it, but I really wanted to use HomeAssistant and see what I could do with it. I hated it a bit less when I started using docker compose. I started loving it when I started using it as a way to explain json to non-programming IT types, trying to explain it without braces and brackets seems to get across easier. I guess its more human readable, but as a result formatting has to be spot on (those indents and spaces replace the need for brackets and braces).

    One useful trick if you truly hate it but need it, write it in json, then just use a converter to change that into yaml.

    • derpgon@programming.dev
      link
      fedilink
      arrow-up
      7
      ·
      edit-2
      2 months ago

      Fun fact, since YAML is a superset of JSON, any JSON is a valid YAML. You can still use pure JSON.

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

      Sorry, what’s confusing the fact that "Hi my name is {$this->name}" works and "Hi my name is {self::name}" is unintelligible gibberish! /s

  • Eryn6844@beehaw.org
    link
    fedilink
    arrow-up
    2
    arrow-down
    2
    ·
    2 months ago

    cradles yaml in her hands and coos don’t you talk to my baby like that! she has potential !

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

    Somehow it’s clunky to use.

    huh?

    I find developing GitHub CI in YAML clunky.

    I don’t find configuring a simple service via YAML config, with a preset showing me and explaining what I can do clunky.

  • Windex007@lemmy.world
    link
    fedilink
    arrow-up
    109
    arrow-down
    25
    ·
    2 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
      31
      arrow-down
      6
      ·
      2 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
        67
        arrow-down
        4
        ·
        2 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
          17
          arrow-down
          5
          ·
          2 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
          24
          arrow-down
          19
          ·
          2 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
            3
            ·
            2 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
            5
            arrow-down
            1
            ·
            2 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
          7
          arrow-down
          6
          ·
          edit-2
          2 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
            ·
            2 months ago

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

        • marcos@lemmy.world
          link
          fedilink
          arrow-up
          13
          arrow-down
          1
          ·
          2 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
            2 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.

      • xmunk@sh.itjust.works
        link
        fedilink
        arrow-up
        37
        arrow-down
        8
        ·
        2 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

        • Eager Eagle@lemmy.world
          link
          fedilink
          English
          arrow-up
          15
          arrow-down
          7
          ·
          edit-2
          2 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.

          • tyler@programming.dev
            link
            fedilink
            arrow-up
            2
            ·
            2 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
              2 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.

          • xmunk@sh.itjust.works
            link
            fedilink
            arrow-up
            13
            arrow-down
            1
            ·
            2 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
              2 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.

        • deegeese@sopuli.xyz
          link
          fedilink
          arrow-up
          22
          arrow-down
          5
          ·
          2 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.

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

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

    • AdamBomb@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 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.

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

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

    • Eager Eagle@lemmy.world
      link
      fedilink
      English
      arrow-up
      11
      arrow-down
      5
      ·
      edit-2
      2 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.

          • ugo@feddit.it
            link
            fedilink
            arrow-up
            1
            ·
            2 months ago

            What “it” is configurable? If the code is indented with 4 spaces, it is indented with 4 spaces. You can configure your editor to indent with 1 space if you want, but then your code is not going to respect the 4 spaces of indentation used by the rest of the code.

            I repeat, the only accessible indentation option is using tabs. This is not an opinion because every other option forces extra painful steps for those with vision issues (including, but not limited to, having to reformat the source files to tabs so they can work on them and then reformat them back to using spaces in order to commit them)

    • marcos@lemmy.world
      link
      fedilink
      arrow-up
      10
      arrow-down
      3
      ·
      edit-2
      2 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.

  • MajorHavoc@programming.dev
    link
    fedilink
    arrow-up
    6
    arrow-down
    6
    ·
    2 months ago

    If YAML and JSON were gripping my hands for dear life, dangling off of a cliff…

    I would let both drop into the abyss so I could spend more time with INI.

  • thingsiplay@beehaw.org
    link
    fedilink
    arrow-up
    6
    ·
    2 months ago

    I don’t like it either, but I’m not entirely sure why. Maybe the biggest flaw to me is it uses Python style indentation for structuring as part of data logic. It doesn’t feel like a configuration language to me and it does not feel simple too. It’s also unlike most programming language structures (maybe besides Python), so it looks weird to read and write. Other than that, I don’t know exactly why I don’t like this format much. Admittedly, I did not do much in YAML, so because lack of experience take my opinion with a thick grain of salt.

    We have JSON and TOML. I quiet like TOML. We have “better” alternatives, that are probably easier to parse. And therefore there is not much need for YAML. Maybe if YAML was the default config format for Python it would get off the ground and be accepted more often.

  • GTG3000@programming.dev
    link
    fedilink
    arrow-up
    7
    ·
    2 months ago

    It’s inconsistent and annoying. Expressive, yes. Gets it’s job done, yes. Absolute nightmare of a spec, YES.

    The fact that JSON is a subset of YAML should tell you everything about how bloated the spec is. And of course there’s the “no” funny things.

    Personally, my favourite way to write configs was using lua (because it was already part of the project so why not), but JSON does fine.

  • Reddfugee42@lemmy.world
    link
    fedilink
    English
    arrow-up
    18
    ·
    2 months ago

    I don’t like a thing, fellas. With that being all I’ve told you, please explain why I don’t like that thing.