Yes. We took the time to learn the language first. We understand things like closures and anonymous functions and understand the value of prototype-based programming. We know how dynamic typing works because we're not morons. We know how 'this' works and understand that the language would be completely broken if it worked like you think it should.

Yeah, I'd call that a 'different mental space' from yours.

It has flaws, sure, but so does every other language. It's also an incredibly clever and well-designed language. You're obligated to learn it first, of course. I know the syntax looks familiar, but it's not Java or C.

I don't get it either. It seems to have an awful lot of trouble maintaining compatibility between minor versions.

It's funny. I was actually quite grateful for this feature -- it came in quite handy on a personal project years ago.

I wouldn't be so quick to count it as a design flaw as lots of languages work that way. C/C++/Java/Python2/Ruby ... it's quite common.

The girl at the front desk doesn't need to know javascript either.

So... what was the point of your 'I don't need it' comment? It's not relevant to the 'ask Slashdot' question or the rest of the discussion.

If your host hasn't upgraded PHP in over a decade, it's time to find a new host.

Why do you want people to be woefully misinformed?

A couple points:

This is wrong. There are no classes. Yes, they are being introduced in ES6 -- which is sure to be remembered as the biggest mistake ever made, despite the fact that they're essentially sugar. Pretending to be 'like java' with constructor functions and new was obviously a huge mistake. Why double-down?

(To everyone else reading) They're quite controversial. Not only are they unnecessary, but they introduce unnecessary complexity -- with no obvious benefit to compensate. It's pretty well established that prototypal OO is superior to classical OO in every way. It's simpler, requiring users to understand fewer concepts and yet it's still far more 'powerful'. On 'powerful' I'll direct you elsewhere as I'm not interested in arguing this point with the kool-aid drinking OO zealots. Search for something like 'prototypes vs classes'. If you have it, put your ACM DL subscription to good use.

(While I'm complaining. Arrows? => Way to introduce inconsistency, ECMA! )

I'd say that this is true for every language. Never judge the quality of a language by the quality of the code you inherit. No language can encourage developers to write 'good' or 'bad' code.

That's the best you could you manage?

Hell, that's not even a problem with the language!

I'd call that a +5 funny ... but this is what many MENSA members actually believe.

You actually believe that such a fence would keep people out?

Amazing.

Cut him some slack, he's just an undergrad. He won't find out that he doesn't know anything until later.

... then larger things again?

(pet peeve)

Still confused, I see. Well, there's not much I can do about it.

Looks good from here.

Which is why it's an excellent example.

Keep at it. You'll puzzle it out in no time.