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

Re: Coordination

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Sat, 13 Apr 2013 16:23:13 -0400
Message-ID: <5169BEB1.5080304@mit.edu>
To: Rick Waldron <waldron.rick@gmail.com>
CC: "public-script-coord@w3.org" <public-script-coord@w3.org>
On 4/13/13 2:33 PM, Rick Waldron wrote:
> Yes, you're right. I'm sorry for over generalizing and I hope that you
> and Chaals will accept my apology.

All is forgiven on my end.

One other thing I think is worth thinking about, in this thread, is that 
new APIs aren't just bad as idiomatic JS, they're often bad in all sorts 
of other ways (e.g. don't even check whether their IDL makes sense or is 
valid).  What we really need to be doing is being more careful in API 
design across the spectrum, and that includes more care about how it 
looks in JS, than we have been, I think.

The problem is that this needs either an editor who really cares (which 
happens, but not always) or feedback as the spec is worked on.  And for 
the latter, I've found that the #1 thing that leads to no feedback is 
that no one knows the spec is being worked on, hence the proposals to at 
least formalize "hey, there's this thing" notifications...  We can and 
should try to do better than that, I think, but that should be a bare 
minimum requirement for specs to proceed that we can implement 

Received on Saturday, 13 April 2013 20:23:42 UTC

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