I think I can do a healthy disagreement without harassment. > Computers should work for us; if they can automate and enforce something, we should let them I a

I think I can do a healthy disagreement without harassment. > Computers should work for us; if they can automate and enforce something, we should let them I agree. But in my experience type hints are often treated as a goal, not as a low cost solution. "We're not going to compromise on type safety". Same happens in TypeScript ecosystem. As you correctly mentioned, Python type hints are somewhat limited. So naturally what happens next is people change the way they write code to work around those limitations. Readability and velocity (major things Python is praised for) gets sacrificed for the sake of "type safety". The promise was for tooling to correct my mistakes. But more often than not I felt that I have to correct tooling mistakes. Before mypy became popular, I often used type annotations because I wanted to. I didn't use them everywhere, I wouldn't enforce them in code reviews, I would never use deeply nested types (those are just unreadable) or generics. I was able to extract value from type hints, they gave me 80% of value for 20% of effort. Static analysis feels like it tries to get another 10% of value for 90% of cost. It's not a good deal anymore.