Has anyone done measurements about perf implications of CSS in JS vs old school stylesheets? Wondering what the trade off is there. 
-
-
Replying to @owencm
I did tons of tests. negligible perf diff, especially with codesplits etc.https://github.com/threepointone/glamor/blob/master/docs/performance.md …
2 replies 0 retweets 4 likes -
Replying to @threepointone
: the load time difference should be large due to parse ; also memory. Code split will minimize, ofc.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @owencm
yeah, this is where the SSR/prerendering kicks in. also, most solutions also dedupe rules, also helps.
1 reply 0 retweets 1 like -
Replying to @threepointone
: right, so *not* actually putting CSS in your JS file? Seems good :-)
1 reply 0 retweets 1 like -
Replying to @slightlylate @owencm
broadly speaking, we’re sensitive to the concerns you’re pointing out, and can mitigate.
1 reply 0 retweets 2 likes -
Replying to @threepointone
: great! Looking for things to recommend to teams who have made this mistake (in addition to Shadow DOM; best answer)
1 reply 0 retweets 0 likes -
Replying to @slightlylate @threepointone
: speaking of, why not generate <template>s in your SSR & inline styles into stamped Shadow DOM?
1 reply 0 retweets 3 likes -
Replying to @slightlylate @owencm
good one! haven’t considered it. (tbf, haven’t felt the need) will def give it a spin once life calms down.
2 replies 0 retweets 0 likes
: gets you some nice things: shadows get their own (faster) style resolver, mimimise global ruleset, real isolation
-
-
Replying to @slightlylate @owencm
ot- twitter could use a RemindMe bot !remindme about this in june
0 replies 0 retweets 2 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.