I would like to summarize some of what we talked about regarding the
ES-next module system in our recent f2f.
Everyone agrees that modularity is the one big remaining item we
would like to move to proposal status, and that we would consider
ES-next incomplete without a solution. Everyone understands that
people today are using static <script> tags, and roll-your-own module
systems using XHR and dynamic <script> tags, at the cost of much
unnecessary boilerplate, duplication of effort and lack of
standardization.
Everyone agrees that Sam and Dave's Simple Modules strawman is an
excellent point from which to start building consensus towards a
proposal.
I will be raising some issues on this list to try and achieve this
consensus. To that end, I would encourage anyone who has not read (or
re-read, in the past 2 weeks or so) Sam and Dave's strawman writeups
to become familiar with them:
Hi folks,
I would like to summarize some of what we talked about regarding the
ES-next module system in our recent f2f.
* Everyone agrees that modularity is the one big remaining item we
would like to move to proposal status, and that we would consider
ES-next incomplete without a solution. Everyone understands that
people today are using static <script> tags, and roll-your-own module
systems using XHR and dynamic <script> tags, at the cost of much
unnecessary boilerplate, duplication of effort and lack of
standardization.
* Everyone agrees that Sam and Dave's Simple Modules strawman is an
excellent point from which to start building consensus towards a
proposal.
I will be raising some issues on this list to try and achieve this
consensus. To that end, I would encourage anyone who has not read (or
re-read, in the past 2 weeks or so) Sam and Dave's strawman writeups
to become familiar with them:
http://wiki.ecmascript.org/doku.php?id=strawman:simple_modules
http://wiki.ecmascript.org/doku.php?id=strawman:simple_modules_examples
http://wiki.ecmascript.org/doku.php?id=strawman:module_loaders
Thanks,
Ihab
--
Ihab A.B. Awad, Palo Alto, CA
I would like to summarize some of what we talked about regarding the ES-next module system in our recent f2f.
systems using XHR and dynamic <script> tags, at the cost of much
unnecessary boilerplate, duplication of effort and lack of standardization.
I will be raising some issues on this list to try and achieve this consensus. To that end, I would encourage anyone who has not read (or re-read, in the past 2 weeks or so) Sam and Dave's strawman writeups to become familiar with them:
strawman:simple_modules, strawman:simple_modules_examples, strawman:module_loaders
Thanks,
Ihab