: (both the delay and the fact that that they yield)
-
-
Replying to @slightlylate @nekrtemplar
where do you think
#webpack could improve (be candid)1 reply 0 retweets 2 likes -
Replying to @TheLarkInn
: webpack (and/or it's users) seem to assume that the biggest problem is size, hence minification/bundling
2 replies 0 retweets 2 likes -
Replying to @slightlylate @TheLarkInn
: the reality, however, is that for most apps the biggest challenge is *how much code you run at startup*
3 replies 1 retweet 7 likes -
Replying to @slightlylate
Isn't that a challenge for the *developer* though, as opposed to Webpack?
@TheLarkInn@nekrtemplar2 replies 0 retweets 1 like -
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
I agree web apps often run too much code at startup; isn't that orthogonal to Webpack tho?
@TheLarkInn@nekrtemplar1 reply 0 retweets 1 like -
Replying to @AdamRackis
: again, this externalization of concerns leads to globally terrible outcomes. Seeing it everywhere /cc
@TheLarkInn@nekrtemplar1 reply 0 retweets 0 likes
: and yes, I'm calling out the frameworks too. But their response is "that's about how you build"
/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.