4 ms·
Quite the opposite, Microsoft changed their font rendering engine to introduce GreyScale (IIRC), But the problem with this new engine is it is horrible on low-d
by 0xFFC 10y ago
Quite the opposite, Microsoft changed their font rendering engine to introduce GreyScale (IIRC), But the problem with this new engine is it is horrible on low-dpi monitor.
Traditionally Windows does have problem with high dpi monitors, but I think there is workaround it (scaling and etc), but with windows 10, fonts on low dpi (by low dpi I mean most of the monitors sold until 1,2 years ago, 20+ inch with 1080p) windows looks like shit (literally). If you are using old framework (WPF and etc) it is okay, because underlying framework is same. Same good old rendering (not in par with Mac or FreeType, but quite acceptable). But if you are using UWP, then quite honestly you are in trouble, in low-dpi monitors. Because Microsoft UWP only does have DirectWrite engine.
The problem with old engine (which is used in Win32, WPF, etc) was it was slow on mobile, and as always Microsoft wanted to compete with Apple and Google on Mobile platform and because they have 99% market share of mobile os. So what is better option than ruining people experience in desktop to force them to switch to WinRT/UWP bullshit ? (I am being sarcastic)
- bayeslives 10y agoCorrect. I use Linux at home. Ubuntu and Mint have nice rendering OOTB, Arch got that great with the Infinality package. OSX also has decent rendering (albeit too fat for my taste), Windows' subpixelrendering + matching fonts used to give sharp letters, yes too skinny, but legible. With their new engine, texts are less legible. The letters are still skinny, but now they're also blurry. All this to cater to the very small fraction that uses Windows on a mobile device; throwing existing desktop users under the bus.