As Xorg is effectively abandoned, these days I run Xlibre[0].

0. https://x11libre.net/

The only HiDPI setting I toggle is Xft.dpi in ~/.Xresources This scales fonts in gtk3, and is used for the scale factor in firefox and Qt apps, and is recognized by most apps using something custom.

How much of this wonderful legacy configurability is supported by Wayback (https://www.phoronix.com/news/Wayback-0.1-Released), so that we can still do this stuff as Wayland replaces X11?

I was there, Gandalf. I was there 3000 years ago, when we edited ~~x11~~ xorg config files by hand. I will gladly pay any price in bloat to never have to touch that nonsense again. Show 3 replies

Creating custom modelines is far from fun activity, bloat or no bloat.

The last time I had to look into that was to work around amdgpu bug that affected screen blinking in KDE Wayland session.

Show 1 reply

"in a simple way" proceeds to write a 300 page epic Show 2 replies

cool if you want to stay with 30-year-old desktops like fluxbox, but I'm not about to give up my KDE when I have plenty of ram to spare - the plasmoids for system monitoring alone are simple to set up and useful. Yes, I know there are standalone alternatives. Some things (imo) aren't worth optimising.

But to each their own - I'm sure someone will be all into "debloating" like the author.

Show 3 replies

> For lightweight WMs there are lightweigh compositors exists.

I think that if you're going to take a holier-than-thou, software purity and perfection stance. You probably should make sure to proofread.

If you're gonna be judgemental about other peoples stances and refuse to admit to the existence of such a thing as a "reasonable tradeoff". Talk down to your audience with section headers titled "Compositor (no, not that thing from Wayland)". Maybe make sure what you've written is actually correct.

Show 1 reply