- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Wed, 21 Jan 2015 11:21:04 -0800
- To: Ilya Grigorik <igrigorik@google.com>
- Cc: Yves Lafon <ylafon@w3.org>, Alex Russell <slightlyoff@google.com>, Travis Leithead <travis.leithead@microsoft.com>, Mark Nottingham <mnotting@akamai.com>, Yoav Weiss <yoav@yoav.ws>, public-web-perf <public-web-perf@w3.org>, "www-tag@w3.org List" <www-tag@w3.org>, Jeni Tennison <jeni@jenitennison.com>
On 21 January 2015 at 10:54, Ilya Grigorik <igrigorik@google.com> wrote: > I believe this is still satisfied. The browser (and/or any other tool) > fetches a single resource, which in turn triggers some cascade of background > actions that fetch necessary subresources. I'm talking about the use cases that .zip files satisfy, not that. I don't know why separating these is a problem. I'm talking about having my NPM module as a single unit (without the usual minification+concatenation mess we see for JS modules today), or I want to email a web page to someone, that sort of thing.
Received on Wednesday, 21 January 2015 19:21:33 UTC