All, While its really interesting to understand how different image formats compress and byte boundaries work, it seems to be a different topic than responsive images and the ideal implementation method, as using optimal or non-optimal compression techniques to serve different images to a different breakpoints/screen sizes/screen formats should result in different image sizes therefore reducing/increasing the overall download size of a page depending upon the chosen image. The focus here needs to be more around which techniques will best work for the wider community on specifying a format/syntax to indicate to the browser which image to download based upon the screen/user/device viewing the web page in question. On Tue, Sep 17, 2013 at 3:43 AM, Andy Davies <dajdavies@gmail.com> wrote: > On 17 September 2013 11:30, Marcos Caceres <w3c@marcosc.com> wrote: > >> >> I guess related - "Image Compression for Web Developers", published on >> the 17th of Sept: >> >> >> http://www.html5rocks.com/en/tutorials/speed/img-compression/ >> >> > > Guy Podjarny's talk from Velocity might be handy for more background on > image formats and how they compress > > JPEG starts here - > http://www.slideshare.net/guypod/a-picture-costs-a-thousand-words18062013/14 > > Andy >
Received on Tuesday, 17 September 2013 14:27:55 UTC