- From: Dirk Pranke <dpranke@chromium.org>
- Date: Fri, 12 Apr 2013 19:37:10 -0700
- Cc: public-script-coord@w3.org, annevk@annevk.nl, Robin Berjon <robin@w3.org>
- Message-ID: <CAEoffTCjZoNrPpz-vUsiXycvar=Fn_mab694s0B1KbOdc+qKUw@mail.gmail.com>
One takeaway I have from both my own recent efforts to understand the state of ES6 and the recent threads on es-discuss and public-script-coord is that I think someone should be doing a better job of outreach for TC39. Most of the official public documentation for TC39 (the Wiki, the meeting notes) is written for the members of the committee much more so than for the interested public. This is, in a sense, entirely appropriate, and consistent with how all the other language standards groups I've been aware of work. But it is hard to interpret for outsiders. To take Anne's question that started these threads, it's almost completely unclear to me as a web-dev how exactly we'd expect ES6 modules will work. There is almost no discussion on the wiki of what changes in HTML and JavaScript pages, for example. Even the http://wiki.ecmascript.org/doku.php?id=harmony:modules_examples page is extremely terse, and gives no discussion of what the exeucution order for the modules and scripts are ... what blocks, what doesn't? (I don't actually want the answers to these questions in this thread). Perhaps we need more JS-developer (or web-friendly) documentation? Maybe some of the member companies should more actively write about upcoming things in ES6 the way they do for new features being added to HTML5? -- Dirk
Received on Saturday, 13 April 2013 02:37:57 UTC