Hacker News Reader

Comment by charlesdaniels | Hacker News Reader

At the risk of over-complicating things, perhaps there could be limits per resource type. 10Mb of images might be reasonable (e.g. for a photojournal), but only 128KB of JS, and 128KB for everything else. Something along those lines.

View on HN

Yeah I was surprised they included pictures in the limit at all -- I mean, sometimes, you need those pictures, and for them to load slower is less important so long as you don't need them to navigate the page.

I’m not surprised. The whole point of it is that you can reasonably load it over 3g.

If you have a few megs of images that never show up because they take too long to load, there is no point.

You dont really need full size/resolution images on a web page.

Yeah true but even with small images, you can hit that cap quickly.

You do for full width retina images on 1440p+ monitors.

You people are why some sites have ugly blurry logos/images on my 4k screen

more the fault of the site devs for not using css media queries, or svg ;p

Does getting in the club assume you have a low resolution screen?

SVG only works in a few places.

If you were able to calculate the space in the document flow for those images, I'm fine with the lazy loading. I hate when the page text appears rendered long enough that I start reading, but then lazily loaded items cause the flow to rearrange the text so that I lose my place.

I imagine it should be pretty easy with javascript to set up dummy images, and replace them... probably also doable in pure css, just make them a block element or something, with a set size...

You don't have to imagine everything. Normally the lazy-loaded image should be seeded with transparent SVG that as the same dimension. It's a solved problem.

Wasn't this what progressive jpeg was invented for?

I miss lowsrc. It had a point.

Well if you need them you can't be a part of this 1MB club.

It's not a bad thing, it's just a thing.

You could use SVG images.

Reply on news.ycombinator.com