Re: Figuring out easier readonly interfaces

On Wed, Oct 2, 2013 at 4:52 PM, Domenic Denicola
<domenic@domenicdenicola.com> wrote:
> From: Boris Zbarsky [mailto:bzbarsky@MIT.EDU]
>> On 10/2/13 5:42 PM, Tab Atkins Jr. wrote:
>>> It's doing that outside of ES, then.
>
>> Yes, of course.  That's what the DOM implementation tends to do: work non-ES-accessible state!
>
> And this highlights the essential problem. As discussed ad naseum on es-discuss, it's impossible to make proxies work faithfully on objects that have private state. (The only solution is membranes, whose effects are much more far-reaching than make sense for this effort.)
>
> An attempt at some proxy-based solution will never work for DOM objects, full stop. Best to consider other approaches.

Yeah, and without proxies, a generic solution is impossible.  At best,
we can produce an opt-in solution that's just less verbose and
error-prone than doubling interfaces.

~TJ