ECMA 5 introduced Function.prototype.bind() which is similar to the
PrototypeJS version that binds the context to the function. In a class
scope you can bind the "this" variable in the function scope to the "this"
of the class.
Here is a performance test between those 2
http://jsperf.com/nati
I believe that the plan all along w/r/t these new JS-core features has been to
prefer the native implementation where available and compatible, and leave the
Prototype method as a polyfill for older browsers. I don't believe that
Prototype currently behaves this way, but the last time I heard an
Chrome on OSX with Prototype winning as well - I was just curious as to why
the native implementation is slower than the Prototype implementation?
Jason Westbrook | T: 313-799-3770 | jwestbr...@gmail.com
On Mon, Jun 3, 2013 at 5:06 PM, Walter Lee Davis wrote:
> I believe that the plan all alon