You were comparing Javascript with the "utter stupidity of its many flaws" to "far more sensible" languages.
"C doesn't bungle such basic things as equality checks, for instance."
2.0 == 2?
False.
Most people would consider that a flaw. As programmers we understand that integers and floats are different in the computer, but that's not how it works in math.
"C also doesn't include idiocy like semicolon insertion."
You must really hate the languages that don't use semicolons at all. :-)
"==" implies that one can be substituted for the other at will without changing the result. In C, that's not the case for 2 and 2.0.
Compilers have gotten a lot better about warning about these situations, but they're far from perfect. In any case, "produces a compiler warning" and "doesn't produce a compiler warning" isn't "==" behavior.
We won't even go into why having a logical comparison return an integer result is questionable. Yes, it's very convenient sometimes, but it's still an example of the type of
"flaw" that he doesn't like in Javascript.
"C doesn't bungle such basic things as equality checks, for instance."
2.0 == 2?
False.
Most people would consider that a flaw. As programmers we understand that integers and floats are different in the computer, but that's not how it works in math.
"C also doesn't include idiocy like semicolon insertion."
You must really hate the languages that don't use semicolons at all. :-)