W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2013

Re: Specs and Object.observe()

From: David Bruant <bruant.d@gmail.com>
Date: Mon, 17 Jun 2013 22:51:30 +0200
Message-ID: <51BF76D2.8040301@gmail.com>
To: Domenic Denicola <domenic@domenicdenicola.com>
CC: Rick Waldron <waldron.rick@gmail.com>, "Mark S. Miller" <erights@google.com>, François REMY <francois.remy.dev@outlook.com>, Marcos Caceres <w3c@marcosc.com>, public-script-coord <public-script-coord@w3.org>
Le 17/06/2013 21:57, Domenic Denicola a écrit :
> What would change notifications look like for a Map, say? My impression of change notifications was that they usually applied to properties, not to general internal mutable state.
People will ask for it eventually. That's the course of things. 
Initially, we had object and properties "Java-style" (objects = 
properties + methods) and then people asked for events on mutable state.
We had Java-style (properties+methods) DOM and people asked for events 
to observe DOM mutations. It seems like an inevitable thing. If change 
notifications for Map don't go through Object.observe, people will ask 
it in some other form. There seems to be a need to be notified of 
changes anytime there is mutable data.

And our Smalltalk/Java cultural legacy when it comes defining object 
interfaces seem to always make us forget events from interfaces when we 
first design them.

Received on Monday, 17 June 2013 20:52:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:13 UTC