Sure, all problems can be solved in theory with things like meticulous documentation, rigorous coding standards that everybody follows and lots of detailed tests. But in practice those sort of informal constraints will break down over years as developers of varying skill levels come and go. Better to formally force as much of that as possible with a decent type system.
Nowadays I will take a static language with automatic type inference over a dynamic language anytime, preferably one that with direct support for FP.
The IDE support, code navigation and refactoring, and runtime performance just beat dynamic languages all the time.
For the few use cases where dynamic types really make a difference, that can be supported by some kind of variant type or reflection.
In my experience a good type system doesn't add much friction and the extra documentation you get from specifying types more than pays for itself in the long run.