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 anything "official" on this list about the future of Prototype, that was one of the things mentioned.
BTW, what browser were you using when you tested this? In Safari.latest Mac OS X, I see Prototype winning, and native 17% slower. Walter On Jun 3, 2013, at 5:44 PM, Jason wrote: > > 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/native-function-bind-versus-prototype-js > > Higher numbers are better as that is the number of operations per second and > the native bind() method is higher? > > Anyone have any insight? > > Thanks all! > > -- > You received this message because you are subscribed to the Google Groups > "Prototype & script.aculo.us" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at > http://groups.google.com/group/prototype-scriptaculous?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
