Webpack+HMR === megawin for my dev workflow. Webpack as a devtool will stay for a long time imho. Even with vanilla.
-
-
I agree! I'm suggesting folks give the vanilla platform a chance before adopting these tools. You might be surprised!
2 replies 0 retweets 0 likes -
WC are landing in FF this year too; already in Chrome, Opera, UC, Samsung Internet, and Safari. You only need polyfills for FF (for a little while) and Edge/IE.
1 reply 1 retweet 4 likes -
Replying to @slightlylate @brianleroux and
Problem with webComponents is lack of server side rendering
1 reply 0 retweets 0 likes -
Replying to @GundersenMarius @brianleroux and1 reply 0 retweets 0 likes
-
Replying to @slightlylate @brianleroux and
Is this good enough performance for a production website? It seems to be aimed at bots, I'm rendering server side for humans
1 reply 0 retweets 0 likes -
Replying to @GundersenMarius @brianleroux and
If you're alluding to this broke "SSR" pattern, don't do that. Just ship less JS.
1 reply 0 retweets 2 likes -
Replying to @slightlylate @brianleroux and
I don't know what the broke SSR pattern is. I want to render server side to have fast initial paint an then apply js as quick as possible and lazily. Server side rendering doesn't necessarily mean js
1 reply 0 retweets 0 likes -
Replying to @GundersenMarius @brianleroux and
Don't do that. What I see in traces is slow initial paints from lack of flushing and too much late-loaded JS, delaying TTI and delivering effectively broken experiences. You've been sold a bill of goods.
1 reply 0 retweets 1 like -
Replying to @slightlylate @brianleroux and
I think we are talking about different things. Do you have an article or something about these traces and what causes slow paints?
1 reply 0 retweets 0 likes
Paint is the wrong metric. Rendered but unusable content is...well, unusable. The metric to optimise for is Time-to-Interactive (which, for RUM, is FID). See:https://developers.google.com/web/updates/2018/05/first-input-delay …
-
-
Replying to @slightlylate @brianleroux and
Oh yes, completely agree, but human reaction time is rather slow, so we have a grace period of ~100ms after paint before having to make something interactive. So render first, make interactive right after, focus on both TTFP and TTI.
2 replies 0 retweets 1 like -
Replying to @GundersenMarius @slightlylate and
BTW, I would love to see some statistics on how quickly on average after an element is rendered it is interacted with. I suspect (at least for our website) that it's much more than 100ms
1 reply 0 retweets 0 likes - 3 more replies
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.