News for hackers. Stuff that matters.
Re:Real-world HTTP/2: 400GB of images per day by joobus on Thursday July 14, 2016 @10:33PM (#12098630)
One way to "solve" the time to visual completion would be to make all the images, but especially the larger images, progressive scan. For very large images, the difference in visual quality between 50% downloaded and 100% downloaded on most devices isn't noticeable, so the page would appear complete in half the time.
Re:Real-world HTTP/2: 400GB of images per day by xzyfer on Thursday July 14, 2016 @10:46PM (#12098669)
Totally. There are a bunch of ways to address the performance issue. As I alluded to at the end of the post there serious technology considerations when preprocessing so much image data.

We're currently looking at whether we can solve use IntersectionObserver for efficient lazy loading of images before the enter the viewport.

Re:Real-world HTTP/2: 400GB of images per day by pornel on Friday July 15, 2016 @02:32PM (#12102912)
There's an excellent talk about doing exactly that, showing a working prototype & results measured:

https://www.youtube.com/watch?v=66JINbkBYqw

Re:Real-world HTTP/2: 400GB of images per day by MichaelGG on Thursday July 14, 2016 @10:50PM (#12098679)
If there's a way to tell it not to render until x% downloaded, sure. Otherwise slower connections see the low-q versions for a while and it can disconcerting. Either to some users or some PMs.
Re:Real-world HTTP/2: 400GB of images per day by xzyfer on Thursday July 14, 2016 @11:31PM (#12098793)
This is correct. Visually completion will not be achieved until the entirety of the images within the viewport are downloaded.

However progressive jpegs could improve initial paint times. These are dynamic so each page would have it's own unique (although related) profile.

Re:Real-world HTTP/2: 400GB of images per day by b34r on Thursday July 14, 2016 @11:26PM (#12098781)
Doesn't that increase the file size though? They're looking at 3G load speeds, so any increase in file size is probably unwelcome.
Re:Real-world HTTP/2: 400GB of images per day by ex3ndr on Friday July 15, 2016 @05:28AM (#12099759)
Progressive JPG almost always smaller than generic one
Re:Real-world HTTP/2: 400GB of images per day by ashmud on Friday July 15, 2016 @01:24PM (#12102508)
OTOH, progressive JPEGs tend to require much more memory to decode. I do not have specific numbers to cite. Only going off of anecdotal usage of image programs over the years (e.g., Java photo uploaders that choked on progressive JPEGs).