But improper use over something as simple as typing (at least typing as implemented by popular languages these days) _should not be a problem_.

If I create a bug by multiplying by a string, I'd ideally find out immediately after writing it, as the background compiler/analyzer detects the problem. Saying "Oh, well, we'll just assume that an integer times a string is 0" is just... dumb.

Seriously, if a program has a bug like that, what's the point of continuing execution? What's the real-world use case for this? The only use case I can see is "people screwing around making a home page, where nothing really matters and if they make a mistake, hey, just try to go on and maybe that last line wasn't really important anyways". It's the Visual Basic "On Error Resume Next" mindset.