4 ms·

Loading this page with JS disabled, all the images are blurred. Loading it with JS, there's a fancy fade-in animation on the images. What is the point of this?

Loading this page with JS disabled, all the images are blurred. Loading it with JS, there's a fancy fade-in animation on the images. What is the point of this? Why would you intentionally distort the images for people who browse with JS disabled?

jbicha 10y ago
because almost everyone has JavaScript enabled because websites are broken with it disabled…
- insertnickname 10y ago
  Because web developers deliberately break websites...
rcarmo 10y ago
It's a simple approach to lazy loading, so that you only download the images you actually want to view on a phone as you scroll to them. (I also pick the right kind of image depending on your display DPI, and resize them on the back-end, but that's beside the point here) I get a _lot_ of mobile visitors, and mobile bandwidth is expensive, so I'm considerate to them - folk with JavaScript disabled know how to re-enable it to view the images, and are a very minute percentage of my page views. Sorry! :)
- abrowne 10y ago
  FYI I also get the blurry images in Firefox's reader mode. (I had to go back to the original to see if that was intentional when I saw the first screenshot ;-)
  - rcarmo 10y ago
    Yeah, well, that's actually JavaScript that (go figure) strips away all the event handlers :)
- matt_kantor 10y ago
  The images did not load at all for me the first time I went to the page. There were just blank spaces at odd places and it wasn't until halfway through the article that I realized there were supposed to be images. I also saw some raw markdown-looking text like "[foo][f]", though other formatting and links rendered correctly. I'm using Firefox 49 on Ubuntu 16.04. I just refreshed again and everything seems to be working now.
nkoren 10y ago
For the same reason that you would intentionally clutter up the document with HTML markup tags for people who are browsing on a teletype machine.

jbicha 10y ago

because almost everyone has JavaScript enabled because websites are broken with it disabled…

insertnickname 10y ago
Because web developers deliberately break websites...

rcarmo 10y ago

It's a simple approach to lazy loading, so that you only download the images you actually want to view on a phone as you scroll to them. (I also pick the right kind of image depending on your display DPI, and resize them on the back-end, but that's beside the point here) I get a _lot_ of mobile visitors, and mobile bandwidth is expensive, so I'm considerate to them - folk with JavaScript disabled know how to re-enable it to view the images, and are a very minute percentage of my page views. Sorry! :)

abrowne 10y ago
FYI I also get the blurry images in Firefox's reader mode. (I had to go back to the original to see if that was intentional when I saw the first screenshot ;-)
- rcarmo 10y ago
  Yeah, well, that's actually JavaScript that (go figure) strips away all the event handlers :)
matt_kantor 10y ago
The images did not load at all for me the first time I went to the page. There were just blank spaces at odd places and it wasn't until halfway through the article that I realized there were supposed to be images. I also saw some raw markdown-looking text like "[foo][f]", though other formatting and links rendered correctly. I'm using Firefox 49 on Ubuntu 16.04. I just refreshed again and everything seems to be working now.

nkoren 10y ago

For the same reason that you would intentionally clutter up the document with HTML markup tags for people who are browsing on a teletype machine.