TLDR re Chrome disabling JavaScript on slow networks: WHY WOULD YOU NOT USE SERVER SIDE RENDERING https://timkadlec.com/remembers/2018-09-06-chromes-noscript-intervention/ …
-
Show this thread
-
The whole concept behind PJAX was basically “hey wouldn’t it be great if instead of reloading the entire damn page we just used JS to grab the bits that need updated to make the current page match the other page? But both pages exist on a server. For search engines.”
1 reply 0 retweets 7 likesShow this thread -
Server side rendering gives you all that. And you still get to use components! What’s not to love?
1 reply 0 retweets 10 likesShow this thread -
But no seriously, is there a reason people wouldn’t be using server side rendering?
16 replies 0 retweets 4 likesShow this thread -
Replying to @rachelnabors
(a) Their build system is so complex—with pages customized for each user—that building & shipping each page is slow, & front end needs JS anyway. (b) (a) but also their audience size is huge & servers are expensive (see Facebook) (c) back end & front end turf war favouritism/etc.
1 reply 1 retweet 3 likes -
Replying to @AmeliasBrain @rachelnabors
For real, though:
@slightlylate can give you numbers about sites that have adopted SSR on top of complex front-end frameworks & ended up with worse performance, because their site still can't *do* anything until the framework is downloaded & hooked up to the server-built markup.1 reply 0 retweets 4 likes -
Which is not to say that SSR isn't a good idea. Just that you can't throw it on top of a site built around front-end frameworks. It needs to be part of a full performance & progressive enhancement plan, building lighter-weight sites that can work without the JS.
1 reply 3 retweets 16 likes
SSR is a great idea, assuming you don't also send all the same script to the client. In every other context, largely a mistake.
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.