[krisajenkins]

Writing JavaScript and feeling you're surrounded by errors is pretty normal. It's a hastily-designed language. There's no getting away from the fact that everything is going to feel a little bit fragile. Just accept it and don't expect perfection.

[muzmath]

Hastily designed for version 0.0.1, this is simply not the case if you are using modern EMCAScript

[krisajenkins]

Is equality still broken? Are maps still broken? Is it still a sporadically whitespace-sensitive language?

[qwertyuiop924]

not AFAIK, but I am not an expert.

[krisajenkins]

Leading questions, I'm afraid. Yes, equality is still broken, maps are broken (and in new & interesting ways in EMCAScript 6), and the language is occasionally whitespace-sensitive.

JavaScript was hastily designed, has never recovered, and shows no sign of ever fixing the fundamental problems. :-(

[muzmath]

Case sensitivity i'm assuming you mean the automatic semi-colon insertion due to a line break after a return statement? I have a hard time seeing this as being a reason to dislike an entire language.

Most languages have features to avoid, JavaScript is no different. Many JavaScript developers use linters to avoid the poor `==` feature. I'm unfamiliar with the argument of the `Map` datastructure implementation being broken. Do you have a reference to that claim?

[qwertyuiop924]

Equality isn't really as broken as people seem to think. And if it bothers you that much, use ===. Yes, it can be annoying, but it works.

What do you mean about maps, and whitespace sensitivity? I've never heard anything about that.