brandon at brandonbenvie.com
Fri Dec 28 06:48:37 PST 2012
What herby said is the reason. There's no compatibility burden for either
those or __proto__ because no version of IE implements either. However
__proto__ still has no alternative, while the accessor functions are fully
replaced by ES5 features.
The only code you'll find in the wild that relies on the accessor functions
is either extremely outdated and non-interoperable web code or lazy Node.js
targeted code (I still don't get why these ever started showing up in
Node.js code, but they do).
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss