3 ms·
Some articles written on this and why it's a matter of opinion: - https://thaomaoh.com/mac-vs-windows/ https://thaomaoh.com/mac-vs-windows/ - https://blog.cod
by chem83 4y ago
Some articles written on this and why it's a matter of opinion:
- https://thaomaoh.com/mac-vs-windows/ https://thaomaoh.com/mac-vs-windows/
- https://blog.codinghorror.com/whats-wrong-with-apples-font-rendering/ https://blog.codinghorror.com/whats-wrong-with-apples-font-r...
- https://www.joelonsoftware.com/2007/06/12/font-smoothing-anti-aliasing-and-sub-pixel-rendering/ https://www.joelonsoftware.com/2007/06/12/font-smoothing-ant...
- https://web.archive.org/web/20160313114920/http://blog.codinghorror.com/font-rendering-respecting-the-pixel-grid/ https://web.archive.org/web/20160313114920/http://blog.codin...
It shouldn't matter if all screens are hi-dpi and it's better to disable font smoothing completely in that case. OSX doesn't seem to support it at all after Mojave.
- mmis1000 4y agoIt's still a bit relevant for CJK, but not as much as it used to be. CJK have some really complex charactrt that hidpi@2 still isn't enough to present perfectly. For example `國` has almost 6 horizontal line from top to bottom. If you are in dpi@2 and set font size to 10. You need to present a correct line with same width within 3 pixels. Which isn't that 'enough'. Although the information density of CJK character is high enough that it is readable even it is somehow blurry. It is not a good reading experience. And what about non-hidpi screen? I don't even know why people are about to read small text of such complex character without sub-pixel anti-alias.
- chem83 4y agoThat's great context. Thank you. We tend to optimize for western use cases, but this is a good example of where that conventional thinking my fail.