Timeline for "Progressive" JPEG: Why do many web sites avoid rendering JPEGs that way? Pros, cons?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 4, 2015 at 19:44 | comment | added | Zdenek | sunk818: While theoretically possible, it would be a cross-layer hack. You would have to parse the JPEG in the TCP part of the stack and interrupt the transfer early... Terrible. And it would break pipelining too. And most JPEG libraries would refuse to work with such file, so you'd have to use a homebrew hack too! Just no. | |
| Oct 4, 2015 at 19:42 | comment | added | Zdenek | Baumr: No, the CPU cost is too high; my phone actually doesn't even partially draw a regular image, it waits for the full load before even displaying. | |
| Sep 11, 2014 at 7:39 | comment | added | Sun | A mobile browser could have a setting to display only the first or second pass of a progressive JPEG by default. This will save on data and provide a faster browsing experience. | |
| Feb 12, 2013 at 10:48 | comment | added | Baumr | I think that mobile is actually a big consideration here — I am guessing that new smartphone support it; and it'll make browsing experience on 3G or slower speeds much better — if you see images that are irrelevant loading, you can leave before you waste more time or money | |
| Sep 10, 2011 at 10:22 | history | edited | Su' | CC BY-SA 3.0 |
added 26 characters in body
|
| Sep 10, 2011 at 10:09 | history | answered | Su' | CC BY-SA 3.0 |