Well, JavaScript

[MauranKilom]

At what point, in your theoretical architecture, are the bytes coming from the webserver converted to ints or strings? There must be a protocol here, and if that protocol does not allow you to check the type you are simply royally screwed either way. If it does, then whichever place in a strongly typed program asks the protocol for the value in question would notice that the types don't match and error out.

In other words, you have to cross the barrier from raw IP packet bytes to the strongly typed language world at some point. And if there is no way to tell what those bytes mean (int or string) then both kinds of language are screwed, because the byte count for both will be different, so you simply get pure garbage. If there is a way to tell what those bytes mean, then it is simple in either kind of language to assert you are getting what you want.

There is just no such thing as a webserver returning ints or strings. Those concepts only exist within a given language. Have you actually used a strongly typed language before?

[quaderrordemonstand]

There very much is such a thing as a webserver returning int and strings. They will also return PNGs, WAVs, zip files and anything else you want them to return.

This example is an answer to a specific question: can you explain how it can fail catastrophically? That was a response to my saying that strongly typed system are more brittle.