Comment by ezluckyfree
5 years ago
That is not the same. Non-integer scaling results in worse sharpness because of the way it needs to be implemented.
See eg: https://tonsky.me/blog/monitors/
5 years ago
That is not the same. Non-integer scaling results in worse sharpness because of the way it needs to be implemented.
See eg: https://tonsky.me/blog/monitors/
That's not true at all. Fonts & other vector-based graphics scale to any resolution just fine.
The myth of 1x, 2x, and 3x being "preferred" is just an Apple-ism because their UI toolkit is pixel-based. That's a flaw in their toolkit, not an inherent technical constraint. Combined with then Apple scaling it yet again after it's rendered.
Other platforms are not nearly as badly designed.
>The myth of 1x, 2x, and 3x being "preferred" is just an Apple-ism because their UI toolkit is pixel-based. That's a flaw in their toolkit, not an inherent technical constraint. Combined with then Apple scaling it yet again after it's rendered.
Apple-ism? Please. Most plarforms and GUI libs are pixel based, and we always have photos to see and other such bitmap assets.
Your photos rarely if ever match the size they are displayed at anyway. What Apple does is the worst possible thing for your photos, which typically end up double resized (once to the app's internal size, then once again for the display scaling).
The largest platform, Android, is not pixel based. The largest desktop platform, Windows, also went through the effort to try and do things properly here, letting the app handle DPI instead and then providing updated toolkits to do that automatically.
> The myth of 1x, 2x, and 3x being "preferred" is just an Apple-ism
And a GTK-ism.
You are not getting any 'sharpness benefit' if your 4k display is showing an upscaled 1080p image.
All applications i use on windows support scaling natively, and provide crisp text at 150%. It's not 2010 any more, this is a solved problem. Anything that doesnt should be killed with fire.