Experimental implementation of Object.observe & JS Utility library now available

Alex Russell slightlyoff at google.com
Thu Aug 23 02:47:20 PDT 2012

On Thu, Aug 23, 2012 at 7:06 AM, Brandon Benvie
<brandon at brandonbenvie.com>wrote:

> I would say it is most definitely not the concern of Observe to watch
> reads and between accessors and Proxies we have all the tools we need for
> that.

I think that misreads the situation. Having proxies available might work
for this, but is it the right (implied) *UI* for it? I.e., if you need to
do half of your work with observe() and then pivot over to proxies for the
other half...that strikes me as strange. There might be good reasons not
to, but saying "you can do it with what we've got" is always tautological
in a turing machine = )

> With the ability to keep present on notifications of changes via observe
> it's actually possible to implement a mirror that can be emit change events
> (by explicitly mirroring changes on the original target changes) and
> provide the benefits of the observe api to listeners, and then implement
> any kind of additional tracking on top of that either by using accessors or
> being a proxy.
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20120823/5b047823/attachment.html>

More information about the es-discuss mailing list