Bruce Eckel has some interesting thoughts.
"How much value do you put on checking as much as possible at compile time?" That oversimplifies the issue. If the type checking came at no cost, then the answer would be as easy and obvious as Pixel implies with his question. I've generally found that most folks who argue that strong static type checking must be preserved and increased at all costs have no experience of a down side because of it. And if you don't see any down side, then you think that arguing against it is obviously crazy.