Bundling vs sending serialized dependency graph

C. Scott Ananian ecmascript at cscott.net
Thu Aug 21 09:01:42 PDT 2014

On Thu, Aug 21, 2014 at 11:54 AM, John Barton <johnjbarton at google.com> wrote:
> On Thu, Aug 21, 2014 at 8:37 AM, C. Scott Ananian <ecmascript at cscott.net>
> wrote:
> Where? The Load Request records imply a dependency graph. Are these
> maintained though out the life of the page? I don't see any existing reason
> to expect these are maintained.

Ian's proposal (well, mutation in general) certainly implies that
these (or an appropriate summary) should be maintained.  Again,
possibly you can drop parts of the graph from memory once all requests
have been fulfilled... but I think that's an implementation
optimization.  The simplest spec would just stipulate a persistent
dependency graph.  I'd guess that you'd want to restrict arbitrary
reads of the graph in order to allow the optimization.  Write-only
access would be best.

> You deleted the context of my comment. I asserted that a build tool was
> needed. Ian claimed the Loader could do it. Now you are claiming I'm wrong
> because a build tool is used.

I apologize if I misconstrued the crux of your disagreement.

More information about the es-discuss mailing list