I've interpolated the image linked in the article (suspect-number-2.JPG) to twice its size, if that helps at all (only in grayscale for now):
http://www.eliteraspberries.com/images/suspect-number-2-749.... (17MB)
http://www.eliteraspberries.com/images/suspect-number-2-749.... (17MB)
Besides, server side he has access to powerful smart resizing programs and algorithms. Client size, not so much.
But I don't see why client-side can't do "powerful resizing". Not since <canvas> appeared, anyway.
You'd still have to move the 5-6 MB original, and then it would hog a lot of people's browsers to work on the image in the canvas (depending on client CPU/memory).
>But I don't see why client-side can't do "powerful resizing". Not since <canvas> appeared, anyway.
Who said it cannot do? I said the options aren't available. The guy did a simple resize. Should he also spend hours coding smart interpolation on javascript instead of just putting the image up?
For most connections, a 17MB download is eaten for breakfast, anyway.
http://code.google.com/p/fftresize/source/browse/fftresize.p...
Like so (edit: note that you'll have to edit the image first to make it grayscale, and even then this uses a lot of memory...):
$ python fftresize.py suspect-number-2.JPG 2.0