• Scrubbles@poptalk.scrubbles.tech
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 个月前

    Iv come to loathe the “pythonic way” because of this. They claim they wanted to make programming easier, but they sure went out of their way to not follow conventions and make it difficult to relearn. For example, for me not having lambdas makes python even more complex to work with. List operations are incredibly easy with map and filter, but they decided lambdas weren’t “pythonic” and so we have these big cumbersome things instead with wildly different syntax.

    • undefinedValue@programming.dev
      link
      fedilink
      arrow-up
      0
      ·
      4 个月前

      Speaking of big cumbersome things with wildly different syntax have you tried a ternary operation in python lately? Omg that thing is ugly. JavaScripts is hard to beat.

      uglyTernary = True: if python_syntax == “shit” else: False prettyTernary = javascript_syntax == “pretty” ? true : false

      • limdaepl@feddit.org
        link
        fedilink
        English
        arrow-up
        0
        ·
        4 个月前

        That’s just because you’re used to it. The pythonic ternary is structured like spoken language, which makes it easier to read, especially if you nest them.

        Is there an objective argument for the conventional ternary, other than „That’s how we’ve always done it!“?

        • Ephera@lemmy.ml
          link
          fedilink
          English
          arrow-up
          1
          ·
          4 个月前

          The conventional ternary is structured like a normal if-else. In fact, in many languages with functional influence, they’re the same thing.

          For example, you can write this in Rust:

          let vegetable = if 3 > 4 { "Potato" } else { "Tomato" };