>Now, there are perfectly valid other reasons to like static typing. I just always hear this one, especially in regards to Python, and it’s really the wrong way

>Now, there are perfectly valid other reasons to like static typing. I just always hear this one, especially in regards to Python, and it’s really the wrong way to look at it. >The extra code and constraints of static typing are liabilities that should have to offer offsetting value to choose them. Agree, agree SO much. After years of only using statically-typed languages, and then switching to Python and Lisp, i never understood why "catching typos and type errors" was touted as the benefit. I also agree they are like a sort-of liability that has to be taken into account in order to turn it around into a benefit. For me, it was mostly performance benefits. Note that not talking about strong typing (vs weak typing). Strong typing is always a good thing.