Standardizing __proto__

Oliver Hunt oliver at
Fri Mar 18 09:20:35 PDT 2011

I believe the current hope is to kill off __proto__ as quickly as is possible.  I'm not taking a position in this argument, this is just my current understanding.

That said your examples environments that support it is slightly misleading as there's only a few JS engines being used between them: Caraken (Opera person is this correct?), JavaScriptCore, SpiderMonkey and V8.   AIR uses webkit so pulls in JSC, and presumably ActionScript as well, although ActionScript is not really an ES engine so i'm unsure if it counts to this discussion.


On Mar 18, 2011, at 9:14 AM, John-David Dalton wrote:

> The __proto__  property has been around for ~13yrs and is now a de
> facto standard supported by Chrome, Firefox, Safari, Opera, Adobe
> Flash, Adobe AIR, Rhino, Ringo, Narwhal, & Node.js.
> It's available on desktops, mobile phones, tablets, and even eReaders.
> The __proto__ property is a powerful language feature that cannot be
> reproduced through any existing part of the language.
> Current proposals like,
>, are too
> limiting, (it's useful for more than just arrays) and don't cover the
> full functionality/flexibility of __proto__.
> I propose making it official by beginning the process of standardizing
> __proto__ or some addition of equal utility.
> More info:
> - John-David
> _______________________________________________
> es-discuss mailing list
> es-discuss at

More information about the es-discuss mailing list