You hate tests, therefore want static-typing. You do realize that static-typing doesn't mean error-free code, right? Even with static-typing, it's probably a good idea to have tests.

>You hate tests, therefore want static-typing. You do realize that static-typing doesn't mean error-free code, right?

As much as you realize that having tests also doesn't mean error-free code.

>Even with static-typing, it's probably a good idea to have tests.

For much less stuff. With a proper compiler, half of the kind of tests people do in Ruby land are totally needless. You can refactor and you know from the first recompile what has broken and where.