[spion]

The difference is that JS has no binding, yet it still allows for first class methods. Thus the OO "illusion" (object owns the methods) is broken: there are no methods, just functions that take an argument named `this`, in a slightly weird way, only when attached to records.

[groovy2shoes]

> The difference is that JS has no binding ... just functions that take an argument named `this`

Associating a name with a value is precisely what binding is.

Frankly, though, I don't understand this comment at all. Care to clarify for me?

[prodigal_erik]

In Python

  b = foo.bar
  b()

correctly invokes the bar method of the foo object. In JavaScript, you have to write

  let b = foo.bar.bind(foo)

because foo.bar gives you a function (not a method) that doesn't remember which object it came from.

[groovy2shoes]

I'm aware of what you have to write in JS, and I'd argue that that's the behavior that's to be expected. I'm actually more surprised by Python's behavior here. Lua works the same way JS does, as does Common Lisp.