ES6 modules (sorry...)
John Barton
johnjbarton at google.com
Mon Jun 16 15:51:49 PDT 2014
On Mon, Jun 16, 2014 at 3:42 PM, caridy <caridy at gmail.com> wrote:
> On Jun 16, 2014, at 5:41 PM, Frankie Bagnardi <f.bagnardi at gmail.com>
> wrote:
>
> > The other big concern here is that in production, very few people are
> going to be loading every JavaScript file asynchronously. If there's
> magic, there needs to be a reasonable way to handle bundling multiple ES6
> files together.
>
> This is completely off target IMO. We want to walk away from bundling, it
> is tedious, it is ugly, it slows down development, it makes debugging a
> pain, it makes bucketing almost impossible, it is just a pain in general.
> Instead, we want to rely on bundling at the lowest level (at the browser
> level), and that's what SPDY/HTTP2.0 brings to the table, and now that
> Apple is onboard, I don't see why we should consider bundling a relevant
> use-case.
>
I thought SPDY was, to quote wikipedia, about: "reducing web page
<http://en.wikipedia.org/wiki/Web_page> load latency
<http://en.wikipedia.org/wiki/Latency_(engineering)> and improving web
security <http://en.wikipedia.org/wiki/Web_content_security>"
How does SPDY help when the issue is lots of small requests ping ponging
back and forth between client and server?
(Do we want to wait for SPDY in every browser before we use ES6 modules?)
>
> /caridy
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140616/1cb8fc44/attachment-0001.html>
More information about the es-discuss
mailing list