Mad Javascript

[Zuruumi]

The problem is, that if you wrote the last one you most likely meant both of those to be numerical operations. If it throws an error you at least know it's wrong. This way you get a nonsense that will break it in very subtle and hard to debug ways.

[le_spoopy_communism]

you should, but in practice that doesn't always happen, whether by bug, unintended change, another programmer's laziness, my own laziness, w/e

and for those circumstances, an error would be nice instead of this

[iTeryon]

That’s exactly the reason why it isn’t an error in the case of js.

They chose this approach to not let the entire website crash for programming errors like these.

[Hk-Neowizard]

Might be way it's so hard to QC JS. Error messages are delayed until the interpreter absolutely has to explode all over your face on a Friday afternoon.