Omg I literally stumbled upon the unix haters handbook off an old JWZ blog last night and was reading it till 2 in the morning. Thank you!
jcranmer · 7h ago
... somehow this is the first time I've realized that you contributed to the Unix Haters Handbook.
(And I've read it in its entirety at least twice!)
encom · 6h ago
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.
tonyarkles · 4h ago
And the perpetual underlying vague threat “if you get your modelines wrong you could destroy your monitor”. I suppose I started with XFree86 and switched to xorg whenever Gentoo did.
MPSimmons · 3h ago
Immediately did ctrl-f "modeline" and was pleasantly surprised
shmerl · 10h ago
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.
No comments yet
davydm · 10h ago
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.
gen2brain · 9h ago
I do not give up on my openbox. I use it with LxQt. Now there is a Labwc, similar to openbox. It uses its XML spec for config and is similar. But I am still on X until all issues are resolved. Can I use openbox on KDE now? It used to be possible, I can choose WM in LxQt. Back then every WM had a --replace option.
hulitu · 8h ago
> 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
KDE is slow. Fvwm is much faster.
Zardoz84 · 7h ago
What drug do you take ?
signa11 · 41m ago
have you even tried it ? it can probably fit in the entire cpu-cache, and run circles around the likes of kde/gnome/…
cbondurant · 9h ago
> 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.
gen2brain · 9h ago
Does FreeBSD even support Wayland? I heard that there is some work.
eikenberry · 9h ago
Yes, they have official docs on how to set it up and use it.
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!)
The last time I had to look into that was to work around amdgpu bug that affected screen blinking in KDE Wayland session.
No comments yet
But to each their own - I'm sure someone will be all into "debloating" like the author.
KDE is slow. Fvwm is much faster.
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...