Coordination (was: ES6 Modules)

Mark S. Miller erights at
Fri Apr 12 09:29:05 PDT 2013

Hi Anne, while I mostly agree with Rick, I also see the scalability problem
you're worried about here. Part of the problem is that so many w3c platform
APIs are designed without any appreciation of JavaScript esthetics, often
it seems without any real JavaScript experience, and with WebIDL as the
design language for working out and discussing these API designs. Due to
heroic efforts by Cameron, WebIDL is now a workable formalism for
specifying such APIs. But as a design language for discussing and working
out the designs, WebIDL systematically leads to APIs hostile to the working
JavaScript programmer.

If more of the w3c's design discussions were phrased in terms of JavaScript
APIs as they would appear in JS, that would help. Once a design is settled,
then re-expressing it in WebIDL probably remains a necessary evil, but one
that would hurt less.

On Fri, Apr 12, 2013 at 8:06 AM, Anne van Kesteren <annevk at> wrote:

> On Fri, Apr 12, 2013 at 3:39 PM, Rick Waldron <waldron.rick at>
> wrote:
> > The "DOM side" should all be subscribed to es-discuss and read it on a
> > regular basis. Additionally, our f2f meeting notes are a great way for
> them
> > to keep up to date, as well as providing a good jump off for questions
> and
> > concerns.
> Given the number of people working on platform APIs that "should"
> seems ever less likely to become a reality. We need a different
> strategy.
> --
> _______________________________________________
> es-discuss mailing list
> es-discuss at

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the es-discuss mailing list