Illustration from WHATWG HTML spec
I don't know about you but I don't like a bit those blurry (still loading...) images on Medium. Very distracting.— Harris Rodis (@harrisrodis) December 29, 2015
That blurry image preloading thing on Medium - is it just me or does it make all images load extremely slowly now?— James Young (@welcomebrand) February 5, 2016
When, as with the Progressive JPEG method, image rendition is a two-stage process in which an initially coarse image snaps into sharp focus, cognitive fluency is inhibited and the brain has to work slightly harder to make sense of what is being displayed.— From Progressive image rendering: Good or evil?
I'm seeing this more and more on Medium posts. Maybe the whole "blur the pictures" stuff isn't a good idea… pic.twitter.com/X8wLBDHHFw— Damien Erambert (@Eramdam) January 8, 2016
@Medium your weird blurry image thing means that when I read an article offline from my Safari Reading List, I don’t get any images 😞— Brad Dougherty (@bdougherty) November 6, 2015
Unfortunately, the standard JPEG header is hundreds of bytes in size. In fact, the JPEG header alone is several times bigger than our entire 200-byte budget. However, excluding the JPEG header, the encoded data payload itself was approaching our 200 bytes.
|Header (mainly Quantization Table and Huffman Table)||Compressed Data|
|Client (mobile app)||GraphQL|
Canny Edge Detector
Just because you can it doesn't mean you should