No-script solution hits memory usage but lessens file sizes
Jehl said he's “not sure it stands to replace the responsive image techniques currently in play”, but is “excited about its potential for complementing them”, and added that the proposed <picture> element offers additional opportunities for control, such as various crops of an image, depending on size and other factors.
In the article’s comments, debate ensued regarding the simpler technique. Clark Pan noted that extremely heavy compression compromises certain aspects of imagery too much, and Srgio Lopes warned there were memory implications when using larger images and scaling them down, through images being “bitmapped when expanded”, which could be a problem on simpler devices such as mobile phones. Developer Anselm Hannemann added that even on the desktop there can be problems, with very large images impacting on performance. Nonetheless, the technique seems like a potential solution for hi-res support for sites that only require the odd piece of photographic content, and where the performance impact will be relatively low.
What techniques are you currently favouring for serving hi-res images? Let us know in the comments.