…from people who seem to refuse to install paredit or coloring plugins for either? ps lisp syntax ftw, it’s a feature!

  • lorty@lemmy.ml
    link
    fedilink
    arrow-up
    5
    ·
    7 months ago

    No, YAML can fuck right off. I hate that this shit format is used for cloud stuff.

      • RecluseRamble@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        1
        ·
        7 months ago

        OK, that’s excessively “convenient” for booleans. But I don’t get the passionate YAML hate, seems like a simple enough language for config. Didn’t have the pleasure (“pleasure”?) to work with it though, so what’s why else is it shitty?

        • magic_lobster_party@kbin.run
          link
          fedilink
          arrow-up
          2
          ·
          7 months ago

          A property can have the wrong indentation and it would still be a syntactically correct yaml. It’s hard to distinguish whether a line is wrongly indented or not. Copy and paste a line and mistakenly use the wrong indentation, and the entire production breaks.

          In json it’s much harder to do similar mistakes.

  • xmunk@sh.itjust.works
    link
    fedilink
    arrow-up
    4
    ·
    7 months ago

    Who hates s-expressions? They’re elegant as fuck…

    Python, on the other hand, deserves all the hate it gets for making whitespace syntactically significant - I even prefer Go’s hamfisted go fmt approach to a forced syntax to python’s bullshit.

    • eestileib@sh.itjust.works
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      7 months ago

      I dgaf about indices starting at 0 or 1, I can deal with case-insensitivity, but syntactically significant whitespace drives me up the wall.

      • Diplomjodler@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        7 months ago

        What’s so hard to understand about it? It’s how you should format your code anyway. Only it’s enforced.

        • magic_lobster_party@kbin.run
          link
          fedilink
          arrow-up
          1
          ·
          7 months ago

          It’s quite often I have to second guess whether the code is correctly intended or not. Is this line supposed to be part of this if block or should I remove that extra indentation? It’s not always entirely obvious. Extra troublesome during refactors.

          In other languages it’s always obvious when a line is incorrectly indented.

        • vrighter@discuss.tchncs.de
          link
          fedilink
          arrow-up
          1
          ·
          7 months ago

          sometimes, a script needs to be edited in a plain text editor, without having access to an lsp or any other dev tools.

  • Litanys@lem.cochrun.xyz
    link
    fedilink
    English
    arrow-up
    2
    ·
    7 months ago

    But s-expressions give you power that other syntax doesn’t. Data and code as one. Besides there is no other syntax than simply that so it becomes much easier to remember random extra things.

    Whitespace on the other hand, I hate with fiber of my being.

    • anti-idpol action@programming.devOP
      link
      fedilink
      arrow-up
      1
      ·
      7 months ago

      Yes definitely. However Rust manages to become extensible and capable of constructing powerful DSLs out of it’s macros without using S-expressions. But I still find them prettier than Rust’s syntax.

  • sajran@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    7 months ago

    So I’m going to say what I always say when people complain about semantic whitespace: Your code should be properly indented anyway. If it’s not, it’s a bad code.

    I’m not saying semantic whitespace is superior to brackets or parentheses. It’s clearly not. But it’s not terrible either.

    As someone who codes in Python pretty much everyday for years, I NEVER see indentation errors. I didn’t see them back when I started either. Code without indentation is impossible to read for me anyway so it makes zero difference whether the whitespace has semantic meaning or not. It will be there either way.

    • TechNom (nobody)@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      7 months ago

      Python decided to use a single convention (semantic whitespace) instead of two separate ones for machine decodeable scoping and manual/visual scoping. That’s part of Python’s design principle. The program should behave exactly like what people expect it to (without strenuous reasoning exercises).

      But some people treat it as the original sin. Not surprised though. I’ve seen developers and engineers nurture weird irrational hatred towards all sorts of conventions. It’s like a phobia.

      Similar views about yaml. It may not be the most elegant - it had to be the superset of JSON, after all. But Yaml is a semi-configuration language while JSON is a pure serialization language. Try writing a kubernetes manifest or a compose file in pure JSON without whitespace alignment or comments (which pure JSON doesn’t support anyway). Let’s see how pleasant you find it.

  • masterspace@lemmy.ca
    link
    fedilink
    English
    arrow-up
    1
    ·
    7 months ago

    Go home OP, you’re drunk.

    And give us your keys, you’ve had too much minimalism to drive.

  • umbrella@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    7 months ago

    one of my least favorite things about python is semantic whitespace. no need to comment on yaml.

    fuck it, parenthesis all the way.