2 ms·
Here’s a simple demo of the difference: https://temp.chrismorgan.info/does-antialiasing-matter.svg https://temp.chrismorgan.info/does-antialiasing-matter.svg I
by chrismorgan 8y ago
Here’s a simple demo of the difference: https://temp.chrismorgan.info/does-antialiasing-matter.svg https://temp.chrismorgan.info/does-antialiasing-matter.svg
If the contrast is high enough (such as black on white), then I find the difference very clearly visible on my 2× Surface Book display, and subtle but definitely present at lower contrasts. You’ve got to get a lot higher than what’s available on the mass market now before you’ll want to drop antialiasing altogether.
What macOS may have dropped is subpixel rendering—trebling probably-horizontal antialiasing precision by knowing the physical layout of subpixels. They won’t have dropped all antialiasing for font rendering, because that would be very visible.
(Note: Firefox seems to be ruining the feColorMatrix, utterly misinterpreting alpha values above 1. This makes the greys disappear to white. And once I turn WebRender on, the second column doesn’t appear at all! I’d check for bug reports on Bugzilla and file one if I didn’t find one, but I should be in bed.)
- miohtama 8y agoFYI there was no visible artifacts on my mobile phone on the page.