The fastest production-ready image resize out there

#1

Post by igordebatur » Tue, Jun 20, 2017, 5:44 PM UTC

The fastest production-ready image resize out there
blog.uploadcare.com

Re: The fastest production-ready image resize out there

#2

Post by metalliqaz » Tue, Jun 20, 2017, 6:06 PM UTC

Every time something like this comes up, I always think that we should be working to incorporate resize into the image format itself. Imagine if there was a raster format that was stored such that low-res versions of the full-res image were stored first, and subsequent sections contained more information, progressively building up detail. Then you could choose to send only parts of the file if you knew the image would be displayed in a small area.

Sort of like the old progressive scan jpegs, but with a more formalized method for bandwidth-saving partial transfers.

Re: The fastest production-ready image resize out there

#3

Post by dmitrymukhin » Tue, Jun 20, 2017, 9:59 PM UTC

metalliqaz wrote: post #2

Every time something like this comes up, I always think that we should be working to incorporate resize into the image format itself. Imagine if there was a raster format that was stored such that low-res versions of the full-res image were stored first, and subsequent sections contained more information, progressively building up detail. Then you could choose to send only parts of the file if you knew the image woul…

well, there's svg) as for raster, first, I don't think you can have infinite sizes as in vector in feasible manner, second, progressive jpegs are already there, maybe we need to teach clients to stop downloading more info when there's enough for certain container.

Re: The fastest production-ready image resize out there

#4

Post by metalliqaz » Wed, Jun 21, 2017, 1:13 AM UTC

dmitrymukhin wrote: post #3

metalliqaz wrote: post #2

Every time something like this comes up, I always think that we should be working to incorporate resize into the image format itself. Imagine if there was a raster format that was stored such that low-res versions of the full-res image were stored first, and subsequent sections contained more information, progressively building up detail. Then you could choose to send only parts of the file if you knew the image woul…

well, there's svg) as for raster, first, I don't think you can have infinite sizes as in vector in feasible manner, second, progressive jpegs are already there, maybe we need to teach clients to stop downloading more info when there's enough for certain container.

that's basically what I was trying to describe