Not the same as #603, as that calls for Jay's Xwayland implemention to be replaced entirely.
I would be interested in a setting that allows xwayland-satellite to be used instead of Jay's Xwayland implementation. There's already support for compositor integration for xwayland-satellite, making things like on-demand activation possible.
The main reason I prefer xwayland-satellite over Jay's implementation is the way it handles HiDPI scaling. Jay's implemention suffers from performance issues, as X11 applications are rendered at a resolution much larger than the monitor's. This also has a side effect of causing text to appear really small, until you set Xft.dpi: 192 inside of X resources.
I'm not sure about the details, but xwayland-satellite renders X11 applications at the native resolution under HiDPI scaling, so it doesn't have the performance issues Jay's implementation suffers from.
Not the same as #603, as that calls for Jay's Xwayland implemention to be replaced entirely.
I would be interested in a setting that allows xwayland-satellite to be used instead of Jay's Xwayland implementation. There's already support for compositor integration for xwayland-satellite, making things like on-demand activation possible.
The main reason I prefer xwayland-satellite over Jay's implementation is the way it handles HiDPI scaling. Jay's implemention suffers from performance issues, as X11 applications are rendered at a resolution much larger than the monitor's. This also has a side effect of causing text to appear really small, until you set
Xft.dpi: 192inside of X resources.I'm not sure about the details, but xwayland-satellite renders X11 applications at the native resolution under HiDPI scaling, so it doesn't have the performance issues Jay's implementation suffers from.