just seen it, looks like an improved alternative to the good old, non standard, Object.prototype.watch ... but<div><ol><li>records are not "struct like", properties might be or might not be there rather than being there with undefined values ... is this heading to not optimal performances in V8 and others?</li>
<li>how is the memory consumption preserved with freshly new created record objects, rather than a single callback as entry point and simply oldValue, newValue passed as arguments?</li><li>why the callback is not simply something like observer(type, object, property, oldValue, newValue) so that a single callback can be still recyclable and no object is created per each change, plus it's easier to retrieve the new value rather than passing through record.object[<a href="http://record.name">record.name</a>] ?</li>
<li>what is the context of each notify call? (this might be in specs already, so I'll check there too)</li></ol><div>I know it's strawman already but if anyone can explain me these points that would be great, cheers.</div>
<div><br></div><div>br</div><br><div class="gmail_quote">On Tue, Aug 14, 2012 at 10:08 AM, Brandon Benvie <span dir="ltr"><<a href="mailto:email@example.com" target="_blank">firstname.lastname@example.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I love it.
es-discuss mailing list<br>
<a href="https://mail.mozilla.org/listinfo/es-discuss" target="_blank">https://mail.mozilla.org/listinfo/es-discuss</a><br>