Hacker News new | past | comments | ask | show | jobs | submit login

> I wasn’t building it for fun: I work for Uploadcare and resizing images has always been a practical issue with on-the-fly image processing.

you ever consider pushing the work entirely to the client with a resize implemented in javascript? that would cut down on bandwidth as well.




Uploadcare supports shrinking images before uploading, https://uploadcare.com/documentation/widget/#image-shrink (I'm one of co-founders)


It's exactly what my previous article "Image resize in browsers is broken" is about )

https://blog.uploadcare.com/image-resize-in-browsers-is-brok...

It originally was written two years ago, so some things have changed. But in general, it is still correct: for most browsers, you need to combine several ugly technics to get suitable results. Though, the quality will have nothing common with quality when you have direct access to hardware.


Why not use asm.js instead of relying on canvas and hacking around browser problems?


1. asm.js is dead in favor of WebAssembly 2. I need a solution for most browsers on most platforms, not for some very recent and most popular


He's scaling images down, not up. Think taking an uploaded smartphone picture (multiple megapixels) and scaling it down to thumbnail-sized images for various screens.


ic - I thought it was just the usual image-downsample-and-upload thing you see everywhere.

even so, if the service is hosting your images in multiple resolutions you could do it all client side at upload time. they'd be trading bandwidth for cpu time.


Bandwidth is more valuable than CPU time when communicating across the wider internet.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: