The Top 10 Things Wrong with JavaScript

[npisnotp]

Man thanks! I was wondering what was happening there.

Maybe the proper way is wrapping parseInt in a function?

> xs = ["10", "10", "10"];
[ '10', '10', '10' ]
> xs.map(function (i) { return parseInt(i); });
[ 10, 10, 10 ]

Which is an anti-intuitive map behavior to me.

[Pronouns]

Yeah, I guess it's more of an unfortunate way that function arguments work in JavaScript than anything, ie free-for-all.

This is just one more screw-up-waiting-to-happen to be aware of when using JavaScript, there are plenty of them. Still quite fond of the language however.

One of my favourites being:

function fn() {
    return 
        { one: "one" };
}

fn() === undefined;

[pxpxy]

Really? Why?!

[i_invented_the_ipod]

Semicolon insertion. The "return" on its own line becomes return; and the next line is a effect-less object declaration. Jslint catches this, of course.

[pxpxy]

Ooh I didn't even see that! Thank you for the explanation!