Isn't that a challenge for the *developer* though, as opposed to Webpack? @TheLarkInn @nekrtemplar
-
-
Replying to @AdamRackis
: but your point is right-on: what's happening here is externalization of concerns /cc
@TheLarkInn@nekrtemplar1 reply 0 retweets 2 likes -
Replying to @slightlylate
: if you talk to React devs, they'll say "you're holding it wrong". Same for build-tools. /cc
@TheLarkInn@nekrtemplar1 reply 0 retweets 5 likes -
Replying to @slightlylate
: what we need now, however, is an recognition that we need to tie code loading to app events /cc
@TheLarkInn@nekrtemplar2 replies 0 retweets 4 likes -
Replying to @slightlylate
: and THAT is why I'm head-over-heels about PRPL. Code loading happens at view construction... /cc
@TheLarkInn@nekrtemplar3 replies 0 retweets 3 likes -
can you show an example of this.
1 reply 0 retweets 2 likes -
Replying to @TheLarkInn
: go run http://shop.polymer-project.org in devtools &/or chrome:tracing. Tap between sections. /cc
@AdamRackis@nekrtemplar1 reply 1 retweet 2 likes -
Replying to @slightlylate
I see html + json loading, but never JavaScript - I assume that's ur point? Where's the js loaded?
@TheLarkInn@nekrtemplar1 reply 0 retweets 2 likes -
Replying to @AdamRackis
: it comes in w/ the imports. But what's really magical is how they're *sliced up*. /cc
@TheLarkInn@nekrtemplar4 replies 0 retweets 2 likes -
Replying to @slightlylate
: lots of tiny (interruptible) executions leaves main thread responsive.... /cc
@TheLarkInn@nekrtemplar1 reply 1 retweet 2 likes
: ...and because of the selective upgrade thing, controls only render *when they're interactive*
/cc @TheLarkInn @nekrtemplar
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.