andi
In my opinion, the problem, which has already been addressed and asked about several times, is clearly the rigid coupling of the display size of the image on the web page and the resolution of the image as it is retrieved from the web server.
This is no longer sufficient for today's high-resolution displays, because with these displays a browser pixel no longer corresponds to a physical display pixel. And it also eliminates the possibilities of subpixel rendering on common desktop monitors. Not to mention what happens when you use the browser zoom. In addition, high-resolution displays have also changed viewing habits, so that nowadays something that used to be standard is perceived as blurred.
My solution, which I therefore propose, is to create the possibility of being able to set the display size of an image (ultimately via CSS) separately from its resolution as retrieved from the web server. (This is basically what I suggested in my workaround above. This workaround, however, is rather cumbersome to handle. Especially with many images of different sizes and requirements).
One variation would be to have a global setting that specifies by what factor the web server fetch is relative to the display size on the web page.
A second variant would be to be able to make this setting for each individual image. E.g. two sizes, one the display size as usual and one the resolution as retrieved from the web server. And/or you do it with a multiplication factor as with the above-mentioned global setting.
This decoupling allows each user to choose the optimum compromise between the desired sharpness of the display (also with the browser zoom) and the amount of data transfer for his or her application.
Of course, it would be best if both variants were available.
HTH - Michael Sy.