>Type systems to me seem to be (I'm not exaggerating) the answer to all software reliability problems (barring social ones).

Yes, but they increase delivery time problems and developer time problems.

In the end, the industry has decided getting something out cheaper and faster is worth more than getting it out correct code-wise but later or more expensively.

Which might make perfect sense -- what's correct depends on business needs -- and some layers might be totally irrelevant (e.g. program design) as to that.

>Personally, I don't understand people arguing against type systems on principle. Sure, they are type systems that suck (e.g. Java) or are otherwise very verbose and thus straining. But that doesn't have to be the case, it's not an intrinsic property of type systems.

No, but not liking type systems might be an intrisic property of some programmers.