So the situation here is fluid, but in general putting your styles in real <style> blocks (rather than inline properties you manipulate via `http://el.style .*`) is both faster and more memory efficient.
-
This Tweet is unavailable.
-
-
Replying to @slightlylate @treshugart
Thats what most cssinjs libs are doing, inline styles is actually not majority
0 replies 0 retweets 3 likes -
This Tweet is unavailable.
-
Replying to @treshugart @slightlylate
yes, but we remove the need for parallelization by SSR and critical css
0 replies 0 retweets 1 like -
This Tweet is unavailable.
-
Replying to @treshugart @slightlylate
What part of SSR are you hoping to remove soon?
1 reply 0 retweets 1 like -
Search engines are not gonna let us remove ssr without loosing SEO benefits. Current support for dynamic pages requires google to spend many resources an afaik every SEO expert would not recommend relying on it.
1 reply 0 retweets 1 like -
I'll keep mentioning this anecdotal evidence from Spectrum until everybody's heard it: - CSR with data fetching after first render: ~0 pages indexed (a couple static ones without data fetches were indexed) - SSR: ~100% of pages continuously indexed all the time
1 reply 4 retweets 22 likes -
This Tweet is unavailable.
The new debugging info in WMT should show causes. Often we see things about modern sites that use SD that aren't related to it. Old version of chromium :-(
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.