Re: [whatwg/fetch] preload, destinations, and module scripts (#486)

> Any new top-level execution goal will likely use the same principles of a module graph at this point.

No, that's not correct. The preloading concerns for service worker vs. page vs. worker are orthogonal to module graph vs. classic script. They're largely about implementation-level things like prioritization and not really related to moduleness.

> Or would there be other concerns with such a change?

My understanding is that would break their integration into other aspects of the system which process scripts in the same way. Maybe it is changeable, but if the motivation is simply avoiding another rel="" value by introducing N new as="" values, it doesn't seem worth it.

> As you know I'm arguing for preload cache over module map.

Yes, that also is not a good decision, I believe. Compared to HTTP/2, the benefits are tiny, whereas if we can create something module-specific that takes care of all the module-related pieces for us and avoids loading the bytes into two separate caches, we're in much better shape.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/486#issuecomment-324743517