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).
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss

Reply via email to