I have the same situation, no, unfortunately there hasn’t been any improvement with mixed DPI or fractional scaling yet, though I believe that is something that will be considered once the codebase has been adequately modernised.
I spend most of my day away from my desk so it’s not a blocking issue for me, I just use my laptop standalone at my desk, might consider swapping my 4K monitor for a 1080p one from my work.
Yep, completely tear free! :)
If you extend your quote to the full context:
Anybody who’s treating others nicely is welcomed.
So their stance is entirely neutral, they make no explicit effort either direction which I believe in their eyes is discrimination.
As a transgender non-binary omnisexual individual, frankly I couldn’t really give a toss.
It’s important to keep in mind that a project, especially an open-source one, is not one voice. Sure, there may be more public-facing figures who may give a project bad PR, but you have to remember the countless people behind that person, and treat a project by it’s actions not it’s prose.
I am also not trying to “convince” you to “join” this project, not everything is a competition. I am sharing my desktop, which I believe is cool because it’s running on a fork of xorg-xserver, that is the purpose of this community.
I’ve never been too fond of Wayland, with it’s corporate sponsors and project architecture that threatens to kill-off smaller desktops and window managers: hurting one of *NIX’s best qualities IMO, it’s fragmentation and user-choice.
So, when I heard about the X11 revival effort, XLibre, and read that they had a mostly stable release, I switched over.
It’s been a drop-in replacement, my package manager (pacman) prompted me that xorg-xserver and xlibre-xserver would be in-conflict, and thus automatically removed xorg-* in favour of xlibre-*. Everything else has just worked.
Immediately off-the-bat XLibre has TearFree enabled by default, which improves the feel of the desktop massively. But that’s about the only change I can “feel”, a lot of the work is under-the-hood with code-cleanup efforts and refactoring.
System Details:
It does exist, but its small and separate from the “conglomonet”, if you will.