Weak typing may be more "developper friendly", but certainly not more "tester friendly" as any tester will tell you that runtime errors are the worst kind of bugs to locate. That force even more the rule of testing every line of code (coverage testing) because a piece of code somewhere buried deep in the code that execute maybe once in 1 million iterations set a variable to a character type and that same variabe will be used in an arithmetic operation later on.

From a tester point of vue, the earlier you catch a bug (compile time), the easier it is to test.

>Sure, that was what I was trying to say here: Strong typing is not neccesarely better than weak typing. In fact I think in many cases weak typing could be way more 'developper friendly'.