Must built-in prototypes also be valid instances? (Was: Why DataView.prototype object's [[Class]] is "Object"?)

Brendan Eich brendan at
Mon Oct 1 12:23:40 PDT 2012

Nah, cheap shot. Let's reason together, not join taboo words.

The built-ins do what they do and it could be considered a botch to 
abandon, but then there's still a scar lying between old and new 
built-ins. And classes have to do one or both (we may want to self-host 
built-ins with classes).

Thus the quest (not mine alone) to make it unobservable whether the 
builtin constructor's prototype is a degenerate firstborn or a 
dressed-up Object instance.


Kevin Smith wrote:
>     I think Allen is absolutely right that the magic incest of current
>     built-ins is not going to scale, is semantically questionable, and
>     should best be abandoned.
> : )  "magic incest".  This is pretty much a perfect response.
> Kevin
> _______________________________________________
> es-discuss mailing list
> es-discuss at

More information about the es-discuss mailing list