Both upscaling and downscaling result in blurriness, though upscaling will generally yield slightly worse results. But downscaling is still going to yield a result drastically inferior to rendering at the correct size. It totally butchers pixel-perfect lines, for example. It’s the sort of hack that would be awful on low-resolution displays, and only becomes even vaguely tolerable on high-resolution displays because it’s still somewhat better than a low-resolution display for a lot of what people are using their computers for, even if for others it renders it legitimately unusable.

If this really is true, I remain utterly baffled, and I maintain my position that it is an obviously stupid idea. Doing it that way just makes no sense to me. The visual result is way worse, it’s more resource-demanding and thus slows things down a little, and it doesn’t really simplify anything for app developers anyway—the only difference is that you have an integer scaling factor rather than a float scaling factor; but all code is still having to perform scaling mappings, and using floats would change roughly nothing (though the changes required in your APIs may need to propagate through a few levels, and GUI libraries will have to decide how to handle subpixel alignment). Windows and Android have both done it properly, so that supporting fractional scaling is no burden whatsoever for developers. You talk of having to ship assets for arbitrary scales, but that’s not a reasonable argument: GUI libraries should always choose the most suitable version of a resource, and scale it to the desired size themselves if it doesn’t match exactly.

The result of taking the proper approach is that users of fractional scaling may get icons being rendered poorly, but images, text, vector graphics, &c. will be rendered precisely and crisply. Meanwhile, this other behaviour people are saying Apple is doing is just guaranteeing that everything is rendered poorly. Surely they’re not actually doing this? Is it perhaps a case of them having erred in making Retina support integral scaling only, but they’ve since made a better version that supports fractional scaling that each app can opt into, but they just haven’t insisted on everyone fixing their stuff yet? (And remember, Apple’s in an excellent position to do such insisting—they do it regularly.) —But as you say, screenshots are scaled at the next integer, which would suggest that yeah, they’re actually doing this mangling system-wide, and there’s no per-app recourse. Thanks for that explanation.

I just find it hard to believe that Apple would truly butcher things this badly. Even if they’ve been known to do weird things a bit like this before, like killing off their text subpixel rendering with no stated justification, to the clear detriment of low-DPI users (and it may still be worthwhile even for high-DPI users).

I can’t check any of this because I don’t use a Mac. There may even not be a macOS device within a kilometre or two of me.