Hacker News Reader

I think using IIIF is why this site is so broken.

Trying to load an image sends 50 separate requests, when the entire image is less than 400kb. This is the exact opposite of what web optimizers try to do, which is combine lots of small images into 1 large one and use clever CSS to show small parts of the image in the right places on the webpage..

View on HN

Whether to tile the image (or use client-side CSS) is entirely up to the developer. If you want to show regions of interest from large objects, it's much better to be able to extract the ROI as an independent image. For example, this scroll is nearly 100Kx4K pixels: https://dpul.princeton.edu/eastasian/catalog/1z40kx353#?c=0&...

Yes, that's fine for images like that, that's several GB in size, but there's a cut off point where tiling becomes less efficient and slower than just downloading the whole image in one request, I'd guess it's around 1/2MB, which a lot of images on this art site are.

Even if the actual efficiency is no where near that, a 1080p jpg fits in that so it's not like people would want the IIIF functionality on images that small anyway.

Reply on news.ycombinator.com