If not, can people point me to another out of the box solution?
My use case is that I don't want to build an entire image preprocessing/thumbnailing pipeline for image uploads. But if I serve the raw image that the user uploaded, they are typically not optimized for the web. Since I am letting the user upload anything anyway, it doesn't matter whether the image processing is secure (e.g., he can totally reverse engineer the js to upload a non-compressed image, but so what). Client side compression is a pretty elegant solution since you won't even have to pay for cpu cost to process the image. If you don't care to keep the original, it will even speed up the image uploads since they are now smaller. I really see no down sides to doing this?
Hmmm... So you're proposing to get a client to download a big jpeg, to resample to the right resolution, then re-upload to the server for other clients to use?
At least for me there's been plenty of times where I just want to m I nify a single image, and potentially on a machine I don't have all my dev tools on.
Also I think this is project is a good side project, regardless if it's really "necessary"
Better in which way? With Web assembly I've heard the performance can be on-par with C. In terms of ease of install: the user requires no setup step or "download". In terms of network performance: Provided caching is setup correctly and code downloads once, I don't see the harm.
Does this project tick all of those boxes to make this production ready? I'm not sure, it certainly looks polished (I haven't reviewed the code).
[+] [-] 11235813213455|6 years ago|reply
Example: https://caub.github.io/misc/optim
[+] [-] zawerf|6 years ago|reply
If not, can people point me to another out of the box solution?
My use case is that I don't want to build an entire image preprocessing/thumbnailing pipeline for image uploads. But if I serve the raw image that the user uploaded, they are typically not optimized for the web. Since I am letting the user upload anything anyway, it doesn't matter whether the image processing is secure (e.g., he can totally reverse engineer the js to upload a non-compressed image, but so what). Client side compression is a pretty elegant solution since you won't even have to pay for cpu cost to process the image. If you don't care to keep the original, it will even speed up the image uploads since they are now smaller. I really see no down sides to doing this?
[+] [-] kinlan|6 years ago|reply
Also. Neat project op, love seeing all new projects that help with image compression.
[+] [-] unknown|6 years ago|reply
[deleted]
[+] [-] londons_explore|6 years ago|reply
What could possibly go wrong?
[+] [-] rhardih|6 years ago|reply
So simple, yet so effective.
[+] [-] kilian|6 years ago|reply
[+] [-] snek|6 years ago|reply
[+] [-] Etheryte|6 years ago|reply
[1] https://tinypng.com/
[+] [-] karim79|6 years ago|reply
[+] [-] thisisitnownow|6 years ago|reply
[+] [-] verisimilitudes|6 years ago|reply
[+] [-] penagwin|6 years ago|reply
Also I think this is project is a good side project, regardless if it's really "necessary"
[+] [-] slig|6 years ago|reply
[+] [-] Forge36|6 years ago|reply
Does this project tick all of those boxes to make this production ready? I'm not sure, it certainly looks polished (I haven't reviewed the code).
[+] [-] unknown|6 years ago|reply
[deleted]
[+] [-] chrisweekly|6 years ago|reply
[+] [-] throwaway5528|6 years ago|reply
[deleted]
[+] [-] samstave|6 years ago|reply
If not, does anyone have a recommendation for which app does this?
[+] [-] fwip|6 years ago|reply
[+] [-] social_quotient|6 years ago|reply