A lot of information in that article is outdated or just wrong. >Applications (or GUI toolkits) must implement their own font antialiasing This is wrong. Near

A lot of information in that article is outdated or just wrong. >Applications (or GUI toolkits) must implement their own font antialiasing This is wrong. Nearly everything uses freetype, and fontconfig has settings for how freetype should render fonts. If your app is not honoring these settings that's a different problem. >Applications (or GUI toolkits) must implement their own DPI scaling. In practice, implementing DPI scaling is trivial for applications that use a canvas. It only becomes a problem if your application renders raw pixels. If you're sending pixels and don't account for DPI scaling then you get a blurry window upscaled with nearest neighbor. That's how it works on windows and mac too, try running a non-DPI-aware application there and you'll see the same thing. It has nothing to do with the windowing system or the toolkit. >forget about OpenGL pass-through, forget about raw compressed video pass-through ... forget about proper output rotation/scaling/ratio change That won't ever be solved in Wayland because Wayland explicitly doesn't touch any of that. That's not to say they won't ever be solved: those things can be added but they probably need to happen at a different level of the stack.