The last time I had to look into that was to work around amdgpu bug that affected screen blinking in KDE Wayland session.
Last time I did that was in the nineties, when I was doing stuff like running CRT monitors at weird resolutions, like 848x612 instead of 800x600 so I know more about modelines and modelines computation than most.
And yet I don't even remember last time I had to manually edit modelines: 38" monitor @ 3840x1600 pixels and 34" monitor @ 3440x1440 are all working with stock Xorg config.
Monitors have been detected fine at their native resolution since, what, two decades now!?
For analog monitors it made sense that autodetection was bad. Digital ones should be reasonably well served by EDIDs that you'd never need to make your modelines, but there are edge cases like the one I described above. Bad EDIDs also happen.
300 pages on explaining things X. I wouldn't say that's bad. Could always be longer.
https://donhopkins.medium.com/the-x-windows-disaster-128d398...
(And I've read it in its entirety at least twice!)
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.
https://docs.freebsd.org/en/books/handbook/wayland/
Here's a 3 year old article going through their freebsd/wayland setup, so it seems like it's been supported for a while now.
https://forums.freebsd.org/threads/example-tutorial-pure-way...
EDIT: of course there's an xkcd for that: https://xkcd.com/963
davydm•6mo ago
But to each their own - I'm sure someone will be all into "debloating" like the author.
gen2brain•6mo ago
LargoLasskhyfv•6mo ago
hulitu•6mo ago
KDE is slow. Fvwm is much faster.
Zardoz84•6mo ago
signa11•6mo ago
LargoLasskhyfv•6mo ago
On more modern systems even less so.
I'd like to see a demonstration of that fastness, which translates into tangible usability benefits. Not some synthetic microbenchmarking shit.
I tried it, because I still know FVWM2. Was refreshing for a while, felt good because I still could 'do it', but that's it.
The only things I can imagine profiting from it would be running stuff which is at the limit for your physical RAM, where every wasted Megabyte decides between swapping to death, or running through smoothly. But then there is IceWM, which is good enough for such cases. With the exception of FVWMs excellent handling of large virtual desktops.
pshirshov•6mo ago
My quality of life didn't improve much in the PIV+ era. I can play 4k videos now, but the software is much slower, UIs are ugly and, more importantly, inconvenient because there are no native toolkits anymore, just the browser and it dictates the idioms UI designers can use.
Also I want local-first software which does not pipe all my shite to some shady guys, not unreliable plaintext storages somewhere in over the continent.
I don't want to pay subscriptions for everything. I still can run what I purchased 15 years ago but I don't have the option to own anything in this modern world.