"Consider whether static rendering or server rendering can get you 90% of the way there. It's perfectly okay to mostly ship HTML with minimal JS to get an experience interactive."
In other words, just serve some HTML so your users can read your content.
On the other hand, your newspaper writers still need to get paid and unless you're a subscriber, that means ads and cruft on your page for ads.
There is no reason why the following MUST be done client-side:
var label = new Label();
var result = await server.getResult();
label.setText(label);
It was this that led me to invent this for one of my own products.Initially, I had thought server-side React would do this, but apparently it's only for first-load.
raises the question. Sorry, it's a pet peeve.
Petitio principii as the conclusion is a restatement of the premise.
Also it's a rant, not a formal logical argument. Go outside, pet a dog, drink a nice beer, stop wasting your time correcting modern vernacular.
Does my text only newspaper article really need all this crap? Like, it's text, with maybe one image or two. Just give me the damn text and cut out the cruft.
Why are browsers now competing with reader modes? We're sending a bunch of data just to have the browser remove it. Just don't send it to begin with!