The gambit of static typing is that the type checker can attest correctness. But the result, if indeed that the type checker does this (provide a mechanism of provable correctness), you still have to deal with protocol bloat that type systems incur. Hence the deeply nested method calls: that's a result of adopting a static type system.
I'm saying that with all that overhead, people still routinely make mistakes using static typing systems. They get the compiler to tell them that they're correct but their code is still not working.
Comments
The gambit of static typing is that the type checker can attest correctness. But the result, if indeed that the type checker does this (provide a mechanism of provable correctness), you still have to deal with protocol bloat that type systems incur. Hence the deeply nested method calls: that's a result of adopting a static type system.
I'm saying that with all that overhead, people still routinely make mistakes using static typing systems. They get the compiler to tell them that they're correct but their code is still not working.