: reality is browser vendors (eventually) do what webdevs demand. A direct result of them not *being* webdevs.
-
-
Replying to @slightlylate @nekrtemplar
: (both the delay and the fact that that they yield)
2 replies 0 retweets 0 likes -
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 @TheLarkInn
: see the beginning of my I/O talk for details:https://www.youtube.com/watch?v=a5X_Ot-R6lo …
1 reply 0 retweets 3 likes -
Replying to @slightlylate @TheLarkInn
: part of this is framework assumptions, some of it is build step assumptions (that support/re-enforce them)
1 reply 0 retweets 1 like -
Replying to @slightlylate @TheLarkInn
: but result is that default build steps for most frameworky webpack-using apps load too much code up front
2 replies 0 retweets 2 likes -
Replying to @slightlylate @TheLarkInn
: my recommendation is to study the traces you get from http://shop.polymer-project.org vs. other sites on a low-end phone
1 reply 0 retweets 1 like -
Replying to @slightlylate @TheLarkInn
: what you'll see is granular (interruptible) code loading and running
1 reply 0 retweets 1 like
: THAT leaves the main thread responsive; not locked up. Kevin goes into details here: https://www.youtube.com/watch?v=J4i0xJnQUzU …
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.