That’s a brilliant solution, but something about it does not sit well with me.
A big part of my job involves optimization, and that means looking at every asset, every http request, and figuring out both its cost and what users it serves.
In this case, for 98% of users are forced to make a http request and load an image that they will never see. Which basically punishes the majority for the benefit of the minority.
While providing valid and useful content to non-javascript users is important, so is the weight of the page.
Again, it’s a great solution, I just wish there was a way to implement it without passing the cost along.
Chris Ellerby
That’s a brilliant solution, but something about it does not sit well with me.
A big part of my job involves optimization, and that means looking at every asset, every http request, and figuring out both its cost and what users it serves.
In this case, for 98% of users are forced to make a http request and load an image that they will never see. Which basically punishes the majority for the benefit of the minority.
While providing valid and useful content to non-javascript users is important, so is the weight of the page.
Again, it’s a great solution, I just wish there was a way to implement it without passing the cost along.
/Chris