>People make logic mistakes that'll fly straight past a type checking compiler too
Which is why I want to be able to focus my mental power on those mistakes, rather than all the other mistakes the compiler will handle for me. There's only so much brain power available, I don't like wasting it.
>In my experience, most of the type related errors I make in Ruby "fall out" when testing functionality anyway
My experience is quite the opposite. So much so that I believe the only way people can actually come to that conclusion is by not realizing how many errors are actually type errors, because they have never used a type system that is expressive enough to be helpful.
Which is why I want to be able to focus my mental power on those mistakes, rather than all the other mistakes the compiler will handle for me. There's only so much brain power available, I don't like wasting it.
>In my experience, most of the type related errors I make in Ruby "fall out" when testing functionality anyway
My experience is quite the opposite. So much so that I believe the only way people can actually come to that conclusion is by not realizing how many errors are actually type errors, because they have never used a type system that is expressive enough to be helpful.