News for hackers. Stuff that matters.
Re:Rendering on the Web by wffurr on Monday August 19, 2019 @02:01PM (#20740095)
That's what the article is pushing for:

"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.

Re:Rendering on the Web by opencl on Monday August 19, 2019 @06:31PM (#20742401)
And of course the article ignores its own device and is a 1.4MB page containing 10x more JS than HTML.
Re:Rendering on the Web by kinlan on Tuesday August 20, 2019 @02:48AM (#20744393)
We are hosted in infrastructure that doesn't let us change this (although we are currently migrating a lot of the content off on to another site that we do control). Like many developers, we can only do what we can with the tools we have, but we are changing it.
Re:Rendering on the Web by _eht on Monday August 19, 2019 @04:52PM (#20741716)
Ads can be done right. It’s rare, but it can be done.