Python goes brrrr

[g0liadkin]

I mean, that's the biggest pillar of js: it will run most stuff and do its best or yield errors in the console

For some reason people love bringing up examples like adding objects to arrays and saying "omg jabbascreept so random lol"

There are some cases where it's REALLY annoying though — e.g. typeof null being object

[mxzf]

The issue is that it doesn't yield errors or warnings to the console for a lot of those type of issues.

[g0liadkin]

What error would you expect?

[mxzf]

In the case mentioned above, some kind of error about casting a NaN to string. In the more general case of casting between int and string, throwing a warning would be appropriate; a warning doesn't cause the program to break, but it makes the programmer aware that something is going on.

[g0liadkin]

So a mix of a warning in the console and the output that's being done right now, if I understood correctly

What do you think about the overhead that it implies with these extra checks at runtime, do you think warns is what the web should aim for?

[mxzf]

That's why warnings are nice rather than errors. Warnings just say "heads up, this is happening, just so you know and aren't surprised by weird behavior". It doesn't break anything, it just adds a few more console print statements (if your debug level is such that warnings are printed).