I currently think of H2 push as being ~appcache. It has all these interactions with the rest of the spec that you can completely avoid by doing something like SW + WebSockets. It just feels like a pretty big thing when we have really good primitives now.
-
-
Also a pretty annoying issue: If you H2 push some modules, you still can't evaluate leaves until you reach them by parsing from the entry point, which means you need all of the modules before you can start executing. We have no "here's a module and plz eagerly evaluate" in H2.
1 reply 0 retweets 1 like -
Replying to @wycats @MattWilcox
Yeah, and since it's a network-level feature, it can't do that. https://www.chromestatus.com/feature/5762805915451392 … is in Canary tho!
1 reply 0 retweets 1 like -
Replying to @jaffathecake @MattWilcox
Does this just load or also eagerly evaluate?
2 replies 0 retweets 0 likes -
Replying to @wycats @MattWilcox
It does everything short of executing it.
1 reply 0 retweets 0 likes -
-
Replying to @wycats @MattWilcox
If it also executed, what would be the difference between it and <script type="module">?
1 reply 0 retweets 1 like -
Replying to @jaffathecake @MattWilcox
It would allow you to fetch a graph of modules (with names) in order from leaves, and execute the leaves as they come. Today, if you have a -> b -> c and you push c, b, then a, you still have to wait for a to evaluate c, because top import in a is what kicks off eval.
2 replies 0 retweets 0 likes -
You can add script type=module tags for b and c.
1 reply 0 retweets 1 like
In general, I wrote that post because I got a lot of responses like this over my years doing web stuff when people didn't really want to dig into a use case. It became a lonely existence :) At minimum, let's really dig into this?
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.