About isNative, is wasting time?
kangax as reply to Diego comment , then Ajaxian as desert with my comments, but three of us completely in the wrong direction. Why isNative? As I though and as Diego Perini confirmed, sometimes we would like to trust the environment itself before we act in a certain way. I wrote about an XMLHttpRequest wrapper for Internet Explorer, but cases are numerous, like a "not compliant" implementation of the Array.prototype.forEach, or others proto, or some injection problems about window.Array, window.String, or who knows what else. Accordingly, since the JavaScript nature is dynamic, widely dynamic, we would like to be sure that a method is as "specs says" rather than how this or that library implemented it. Can we trust an unreliable environment? The first error we all committed was to find the "best way ever" to understand if a function/method has been changed, without considering the fact that the function isNative itself could be a fake ! No matter how goo...