Oh right, my mistake. s/pretend a bool is a string or vice versa/not know whether an object even has a certain method because it isn't added until runtime/ I'

Oh right, my mistake. s/pretend a bool is a string or vice versa/not know whether an object even has a certain method because it isn't added until runtime/ I'll grant you that this type of thing is more difficult in static languages. But in my experience, the need for this kind of dynamic behavior is quite rare in terms of lines of code. So I'll trade it away any day of the week for the ability to reason about my code with more guarantees. At their core, all bugs are situations where the programmer's expectations didn't match reality. In my experience programmers who are good at debugging are good at being able to question as much of what could be going wrong as possible. Strong static types are about reducing the amount of things we have to question.