News for hackers. Stuff that matters.
Re:Rendering on the Web by vorpalhex on Monday August 19, 2019 @01:51PM (#20739990)
This is insightful and deep, but it begs the question:

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!

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.
Re:Rendering on the Web by Etheryte on Monday August 19, 2019 @01:59PM (#20740078)
This is an excellent point and something I'd like to see discussed more broadly. Gzipping and minimizing assets pales in comparison to simply not sending a bulk of the content to begin with. It would be great if browsers could set a header value when requesting a page, and if supported, the server could respond with content that's already in what would otherwise be the so-called reader format.
Re:Rendering on the Web by ng12 on Monday August 19, 2019 @04:00PM (#20741258)
Because the ultimate goal of the site is not to serve you news. If it was, it'd just be an FTP server or a CDN. The site exists to track you and sell advertising space, end of story.
Re:Rendering on the Web by cheez on Monday August 19, 2019 @05:52PM (#20742166)
The thing that bothers me is we should be able to do lightweight SPAs with server-side rendering.

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.

Re:Rendering on the Web by markdown on Monday August 19, 2019 @10:24PM (#20743357)
> begs the question

raises the question. Sorry, it's a pet peeve.

Re:Rendering on the Web by vorpalhex on Monday August 19, 2019 @11:42PM (#20743648)
> 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.

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.