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.
I'm saying that yes, but (1) maybe modulepreeval, and (2) not because I want that side effect, but just to allow interleaving of fetch/eval and control latency.
-
-
hmm, I agree with https://twitter.com/matthewcp/status/931200843692625920 … then
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I think you are saying you want module loading, but without the deterministic execution, right? AMD worked this way IIRC.
-
Fine, I'll write it up. Probably will be noticed in a year or two ;)
#StoryOfMyLife -
So I take this to mean this is *not* what you're after? I'm really trying to understand. I *do* see the appeal of non-deterministic execution.
-
It's not really about determinism. It's about letting a smart server push a leaf first in response to a top-level request and have the browser eval it right away.
-
I've been pondering if I can force this through service worker lately. You can .postMessage to clients; would at least allow experimentation
-
That's my plan.
-
Just tired of "H2! Solves everything!"
@jaffathecake's posts are one aspect. This is another. We have miles to go before we sleep, and should keep pushing forward without H2 reliance for the time being. SW is great!
End of conversation
New conversation -
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.