B.3.1 The __proto__ pseudo property

Andreas Rossberg rossberg at google.com
Thu May 9 02:09:38 PDT 2013


On 8 May 2013 22:58, Brendan Eich <brendan at mozilla.com> wrote:
> Andreas Rossberg wrote:
>>
>> On 8 May 2013 18:06, David Bruant<bruant.d at gmail.com>  wrote:
>>>
>>> Le 08/05/2013 08:01, Andreas Rossberg a écrit :
>>>
>>>> On 8 May 2013 07:10, Mark Miller<erights at gmail.com>  wrote:
>>>>>
>>>>> What would be gained by
>>>>> moving the property alone to Annex B? If nothing, then I think this
>>>>> consistency should win.
>>>>
>>>> JavaScript implementations in new or existing eco systems that are not
>>>> poisoned by web legacy wouldn't be obliged to support it. It's the
>>>> difference between acknowledging web reality and forcing web reality
>>>> on everybody.
>>>
>>> What are you saying? V8 releases versions where annoying and ugly de
>>> facto
>>> standards are out so that software built on top of Node.js, MongoDB and
>>> other embedders only use a cleaner JS? Awesome! ;-)
>>
>> That would be an option -- I'd very much like to move some of these
>> things behind a flag.
>
> But not __proto__ -- dream on if you think that is going away any time soon!

I was thinking about V8 embedders other than browsers who could toggle
that flag. And I absolutely do think that should be an option
supported by the spec. To Annex B with it! (And let's bury
setPrototypeOf quickly.)

/Andreas


More information about the es-discuss mailing list