• Eager Eagle@lemmy.world
    link
    fedilink
    English
    arrow-up
    17
    arrow-down
    2
    ·
    1 day ago

    You can totally write heavy duty things if you know what you’re doing: use type hints, static checkers, tests, etc. It just takes a bit more effort and care.

    • ByteJunk@lemmy.world
      link
      fedilink
      arrow-up
      11
      arrow-down
      1
      ·
      1 day ago

      But why would I use something that takes more effort and care?

      I’m sure you’re right and it’s possible, but if I don’t have to fix another python project at work I’ll be in heaven.

      • grue@lemmy.world
        link
        fedilink
        English
        arrow-up
        15
        arrow-down
        1
        ·
        1 day ago

        Because “more effort and care” in Python is still way less of a pain in the ass than the minimum enforced boilerplate necessary in most other languages.

          • grue@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            19 hours ago

            Implement a basic socket connection in C (20 lines of manipulating struct sockaddrs and such), then do the same in Python (2 lines).

            And then go back and make the C version support IPV6, because your initial implementation didn’t.

            • “Look, Python is way easier to use than other languages! Look how complex this easy task is in Python versus other languages like assembly and brainfuck!”

              I’m not saying “do stuff in C it’s easier than Python”, but if I took e.g. C# then it’s also just two lines. That supports everything and is also faster than the Python implementation.

      • Eager Eagle@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        19 hours ago

        it’s more effort and care compared to a throwaway script, not necessarily compared to other languages

    • Ephera@lemmy.ml
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      1 day ago

      Personally, my estimate doubles when we’re asked to implement something in Python…

      • Eager Eagle@lemmy.world
        link
        fedilink
        English
        arrow-up
        9
        ·
        1 day ago

        That’s a proficiency matter. Python is the language I can get something done the fastest today, but 6 years ago that would be Java or even JS for me.

        • fuck_u_spez_in_particular@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          9 hours ago

          Nah it’s also a language matter. People complain about Rusts complexity, meanwhile I complain about everything else in other languages, and am faster than in any other language, not necessarily because writing code is faster, but because I am able to just focus on writing code. I cannot tell that about other languages, because e.g. the packaging system is bad, or configuring an environment, or debugging stuff which a strong type-system would have caught already. Also IDE experience I think is the one thing that keeps me away from dynamic languages. Rust analyzer is so much better than anything else I’ve tried, and it keeps getting better (e.g. recently it was added to show whether a trait is object safe or not, and why it is not).

          Another thing that is often missed when comparing static with dynamic languages is just performance, python heavily relies on stuff written in a system language, as soon as a hot-loop is written in python, things get bad

        • Ephera@lemmy.ml
          link
          fedilink
          English
          arrow-up
          2
          ·
          19 hours ago

          Eh, it’s most definitely part of it, but the biggest time sink that I expect when working with Python is fixing the build system every two weeks on different devs’ PCs. I do imagine, if you eventually find a solution that works on most PCs that this workload will go down, but we had a substantial Python part in my previous project and over the course of the 1½ years that we worked on it, it really felt like we were making negative progress. Near the end of it, I couldn’t use PyCharm anymore, because I couldn’t figure out for the life of me, how to make it recognize the dependencies again.