Re: All ECMAScript attributes should be non-configurable

On Sep 30, 2011, at 11:18 PM, Travis Leithead wrote:

>>> +IE9 (another example using configurable properties--as accessor properties on the prototypes). We did work around the performance issue using caches, as most sites don't mess with the configurability of the properties.
>> What performance issue are you refering to? Brendan's argument was actually that this design was better in terms of performance.
> The performance issue was the introduction of ECMAScript5 setters (which much be checked for anywhere in the prototype chain before assigning an own property).

The progenitor was setters and getters in SpiderMonkey, which work the same as in ES5. This spread to non-IE browsers when launched in 2005 with a JS DOM emulation for non-IE browsers that assumed Firefox and SpiderMonkey, in particular __define[GS]etter__. The evolution at Apple and Opera was very fast.


Received on Friday, 30 September 2011 23:03:43 UTC