[Arch-TK]

The only wayland compositor that I know of that handles XWayland correctly is hyprland.

And when I say correctly, I mean that if I am on a non 96 DPI display, e.g. a 168 DPI display (1.75x) and want things scaling properly, Xwayland gets told to pretend that the display size is some resolution in the vicinity of ~1097 by ~686 (not sure how this part works, and honestly I don't think it's relevant) and a DPI of 96. Then xwayland does the most idiotic thing imaginable, it takes the output of applications running under it and stretches it.

And now I have vaseline on my screen.

No thanks.

I may try hyprland at some point to see if there's actual value to using Wayland over X but so far every time I've tried to switch it has been random obstacle after random obstacle.

One of the most baffling has been arbitrary restrictions on the scaling factor.

[WesolyKubeczek]

KWin/Plasma have a switch in the settings where you can toggle vaseline on or off. If you run modern X11 applications that are HiDPI-aware, or you can crank the size of fonts and controls however you want, you may turn it off. If you have that Athena widget application that is tiny otherwise, you turn it on (alas, there is no possibility to have two sets of X display and putting apps on the one you need).

The only thing that for some stupid reason can't be solved is that I can't turn off blurry interpolation on the low DPI applications. Come on! The low DPI layer is in integer multiples, make it nearest-neighbor pixelated but crisp! How hard is that!?

(same goes for QEMU. Argggh!)

[Arch-TK]

Okay, so there's _two_ options now which handle this properly. One conventional desktop environment, and one tiling window manager.