News for hackers. Stuff that matters.
Re:The specification for native image lazy-loading is merged... by edmundsauto on Wednesday February 12, 2020 @11:54PM (#22315416)
No there's not. Web bloat is a problem, but it's not useful to compare media-rich audio-video capable applications with the lightly formatted, text-only, Kindle book format.
Re:The specification for native image lazy-loading is merged... by taeric on Thursday February 13, 2020 @01:20AM (#22315713)
I'm comparing content to content. Yes, some is media rich, but if I want media heavy, I'm likely using Netflix/Youtube or similar anyway. If I'm using a web page, I actually actively don't want media heavy content.

And you can get graphic novels on Kindle nowadays. To pretend it is just text is to undersell the formats now. Could I claim they are bloating? Certainly. Still have a long way to go before they reach current web browser bloat. Which only seems to be marching on. With no signs of restraint on what to pursue.

Re:The specification for native image lazy-loading is merged... by egypturnash on Thursday February 13, 2020 @12:13AM (#22315473)
It’s also not useful for a web page you’re visiting for a few tens of kilobytes of text and a few images to be a media-rich audio-video capable application full of trackers and ads-that-might-be-malware.
Re:The specification for native image lazy-loading is merged... by Kaiyou on Thursday February 13, 2020 @08:50AM (#22317679)
Well, in my book webpages are there to display mainly text and maybe an image. So the comparison seems useful to me.