- From: Dimitri Glazkov <dglazkov@google.com>
- Date: Tue, 16 Apr 2013 15:13:06 -0700
- To: Daniel Buchner <daniel@mozilla.com>
- Cc: John J Barton <johnjbarton@johnjbarton.com>, Scott Miles <sjmiles@google.com>, William Chen <wchen@mozilla.com>, Rafael Weinstein <rafaelw@google.com>, Rick Waldron <waldron.rick@gmail.com>, Dave Herman <dherman@mozilla.com>, Allen Wirfs-Brock <allen@wirfs-brock.com>, Boris Zbarsky <bzbarsky@mit.edu>, Jonas Sicking <jonas@sicking.cc>, Blake Kaplan <mrbkap@mozilla.com>, public-webapps <public-webapps@w3.org>, Steve Orvell <sorvell@google.com>
On Tue, Apr 16, 2013 at 3:07 PM, Daniel Buchner <daniel@mozilla.com> wrote: > One thing I've heard from many of our in-house developers, is that they > prefer the imperative syntax, with one caveat: we provide an easy way to > allow components import/require/rely-upon other components. This could > obviously be done using ES6 Modules, but is there anything we can do to > address that use case for the web of today? Yes, one key ability we lose here is the declarative quality -- with the declarative syntax, you don't have to run script in order to comprehend what custom elements could be used by a document. :DG<
Received on Tuesday, 16 April 2013 22:13:34 UTC