The Linux Thread - The Autist's OS of Choice

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
The plethora of different Wayland implementations is not a good thing, and I'm tired of pretending it is.
Try taking a screenshot in Wayland. In KDE, only Spectacle works. In Gnome, only gnome-screenshot works. If you don't like it, tough shit!
I'm not particularly seasoned in Linux so maybe you mean something extraordinarily specific but I complained about Spectacle upthread when I swapped to KDE Plasma and found Flameshot to be much better as a screenshot/clipping tool
 
I'm not particularly seasoned in Linux so maybe you mean something extraordinarily specific
Because Wayland itself is so minimal, every single Wayland compositor (Gnome, KDE, wlroots, Hyprland) has their own way of getting features not included in stock Wayland working, which in the end makes them all mutually incompatible with each other.
This includes basic features such as:
- Global Keyboard Shortcuts
- System trays
- Screenshots
- Screen Recording
Mostly removed for "security" reasons but I imagine that's just a cope for them being lazy.
If a program doesn't separately write in code to support every single Wayland compositor (which requires significantly more manpower then just supporting X), it either won't work or will be missing features (KeePass Autotype and OBS immediately come to mind). Its why so many programs have trouble with supporting Wayland.
Or you can just use X. Like a sane person.
I complained about Spectacle upthread when I swapped to KDE Plasma and found Flameshot to be much better as a screenshot/clipping tool
Flameshot is really nice, I use it where it works great (on Windows and X11) but was quite buggy on all Wayland compositors (at best) last time I tried it.
 
Because Wayland itself is so minimal, every single Wayland compositor (Gnome, KDE, wlroots, Hyprland) has their own way of getting features not included in stock Wayland working, which in the end makes them all mutually incompatible with each other.
This includes basic features such as:
- Global Keyboard Shortcuts
- System trays
- Screenshots
- Screen Recording
Mostly removed for "security" reasons but I imagine that's just a cope for them being lazy.
If a program doesn't separately write in code to support every single Wayland compositor (which requires significantly more manpower then just supporting X), it either won't work or will be missing features (KeePass Autotype and OBS immediately come to mind). Its why so many programs have trouble with supporting Wayland.
Or you can just use X. Like a sane person.

Flameshot is really nice, I use it where it works great (on Windows and X11) but was quite buggy on all Wayland compositors (at best) last time I tried it.
it sound like wayland isn't a complete utility but a specification, like the difference between an architect that works with the engineers and contractors to actually build a place and one that throws a design draft in your face and says "figure it out yourself"
 
The arguments I've seen in this thread on the wayland vs xorg debate, are some of the most retarded I've come across on the subject. I can't tell if people are just pretending to be retarded to try to make the other person mad. I hope so for everyone's sake. It's sad otherwise.
I acknowledge the fact X11 is behind, and I understand that people won't like developing on this platform. But Wayland is removing the freedom of customizability and things a program can do. Wayland and Rust people are dogmatic people trying to force others what to use.
Most X11 users are fine with people using other stuff, as long as they are not forced to use only one thing.

I should have said before in this thread that I have used Wayland 3 months ago when I reinstalled EndeavorOS and many things didn't work. While some issues were solved, it was still broken. The worst things were the lack of NVIDIA-Optimus support, incompatibility with old X11 mouse cursor themes, lack of Screensaver support, Hotkey limitations, and WINE issues. For me it is unsatisfactory, and I prefer X11, despite the tearing issues.
 
From reading this thread there are apparently Linux users who don't run their own local DNS server so they can look up the devices on their network and then apply their own curated set of blocklists.

I just realized there's probably at least one person here who doesn't run their own Stratum 1 NTP server. Which is then enforced to be used by redirecting *.pool.ntp.org and the Apple and Microsoft time server addresses using the above DNS server to local NTP only. Then have the firewall redirect any remaining port 123 traffic that doesn't obey the DNS to the local NTP servers as well. And finally have a dedicated monitor in the living room showing the NTP status at all times.
2025-06-15_09-26.webp

Amateurs.
 
From reading this thread there are apparently Linux users who don't run their own local DNS server so they can look up the devices on their network and then apply their own curated set of blocklists.

I just realized there's probably at least one person here who doesn't run their own Stratum 1 NTP server. Which is then enforced to be used by redirecting *.pool.ntp.org and the Apple and Microsoft time server addresses using the above DNS server to local NTP only. Then have the firewall redirect any remaining port 123 traffic that doesn't obey the DNS to the local NTP servers as well. And finally have a dedicated monitor in the living room showing the NTP status at all times.
View attachment 7507416

Amateurs.
We're all very proud of you
 
it sound like wayland isn't a complete utility but a specification
That's exactly what it is. A protocol spec, written by gnomeists to cater to their foot-fetishism. There's a reference implementation called Weston, but it isn't widely used.

The annoying part is, there's no actual issue with the idea of writing a common protocol and having multiple implementations. X11 is, ultimately, also a protocol, with XOrg being the most popular implementation. The problem is that Wayland is a shit protocol, with multiple huge gaps that the Wayland organisation refuse to address or claim are for "security". It breaks shit in exciting new ways though, so it's popular with the sort of people who work for red hat (a software support and licensing company that makes more money if things don't work properly).
 
I do not agree with the idea that developers who have experience working in both X11 and Wayland all love Wayland. For example, here is KiCad's view of it:
KiCad does run on Wayland systems, but with significant limitations and known issues that substantially degrade the user experience. While you can design PCBs using KiCad on Wayland, you will encounter numerous problems that we cannot fix at the application level.

These problems exist because Wayland’s design omits basic functionality that desktop applications for X11, Windows and macOS have relied on for decades—things like being able to position windows or warp the mouse cursor. This functionality was omitted by design, not oversight.

The fragmentation doesn’t help either. GNOME interprets protocols one way, KDE another way, and smaller compositors yet another way. As application developers, we can’t depend on a consistent implementation of various Wayland protocols and experimental extensions. Linux is already a small section of the KiCad userbase. Further fragmentation by window manager creates an unsustainable support burden.Most frustrating is that we can’t fix these problems ourselves. The issues live in Wayland protocols, window managers, and compositors. These are not things that we, as application developers, can code around or patch.

We are not the only application facing these challenges and we hope that the Wayland ecosystem will mature and develop a more balanced, consistent approach that allows applications to function effectively. But we are not there yet.

More details: https://www.kicad.org/blog/2025/06/KiCad-and-Wayland-Support/

Their recommendation? Use X11-based desktop environments. - So yeah, not really positive and as a mostly hobby developer myself I can only say my experience has been very similar when I tried to port some of my scripts over from my X11 environment. There are probably ways they can deal with it, same with how Global Hotkeys can use portals, but the issue is that this sometimes come with their own problems or aren't compatible to what you want to do. The point is that it's not really an equivalency and is a regression for many use cases. It's all done for "security", but it's way too locked down. An up to date X11 would be welcomed by many people, the better question is if XLibre can do it, but the will is clearly there.
 
Last edited:
I do not agree with the idea that developers who have experience working in both X11 and Wayland all love Wayland. For example, here is KiCad's view of it:
Um, this guy sounds like a massive bullshit artist. Why does he want his 33 year old application to be compatible across multiple operating systems and JUST WORK?

Any Gnome developer worth his programming socks looks forward to completely rewriting his unoptimized Python hobby application from scratch every couple of years to support GTK5/6/7 with less features than ever before. They don't WANT stable interfaces, they don't WANT functioning compatibility layers, they don't WANT a new system that's supposed to completely replace the one that's worked for most of our lifetimes to have the basic features that were established as necessary more than four decades ago. They WANT to continually chase changes that were done incorrectly and didn't need to be made and shouldn't have been made. That's what it's all about.
 
From reading this thread there are apparently Linux users who don't run their own local DNS server so they can look up the devices on their network and then apply their own curated set of blocklists.
Imagine not running Pi-Hole with unbound on your homelab SFF PC for an independent DNS server with domain filtering. Shit's documented so plainly even a chimp could set it up. However, if running the NTP server requires a hardware atomic clock expansion card then yeah no fucking wonder most people don't self-host that shit. Setting it up to rely on something like DCF-77 would be even more complicated.
 
Mostly removed for "security" reasons but I imagine that's just a cope for them being lazy.
I also suspect the long game. as mentioned redhat makes more money if shit doesn't work, but if they're the ones in charge of what gets implemented and can push it, it becomes the de facto standard. it's basically how microsoft has been operating for decades and became the company it is today.

or put more simple "you'll all use gnome and the way we do things eventually anyway" (especially with them in charge of the only other alternative, what a coincidence).

that's why I really hope xlibre takes off, only to take a big fat dump on that faggy scheme.
 
Last edited:
Where's Solus on the Linux rankings?
Theory-first analysis: Bespoke package manager, NIH symptoms. Might work great. IDK. Another interesting data point to watch, given how Xorg features in its Technologies list ( https://getsol.us/solus/technologies/ ). Interesting dependency-focused build system. Solbuild seems neat. They write a lot of code in Go. Budgie is written in Vala, the weird GTKObject-based language.

Seems a sensible choice for someone who likes Mint, but rough edges will be weird to solve because it's not "like" most other distroes. No idea how readily you'll find them. Project gives a very polished, consistent vibe, devs seem like they're not resting on their laurels.
 
Alright guys, I need some input: FreeBSD or OpenBSD? Gut says OpenBSD cause no CoC cancer and much higher focus on cleanliness & security, but then FreeBSD is bigger, has more packages, and is allegedly easier to configure and troubleshoot. I have never used a BSD system before, so thoughts & advice are appreciated. The host machine will be an X230, which I'm pretty sure should have good hardware support for both.
 
Alright guys, I need some input: FreeBSD or OpenBSD? Gut says OpenBSD cause no CoC cancer and much higher focus on cleanliness & security, but then FreeBSD is bigger, has more packages, and is allegedly easier to configure and troubleshoot. I have never used a BSD system before, so thoughts & advice are appreciated. The host machine will be an X230, which I'm pretty sure should have good hardware support for both.
FreeBSD has the linuxulator which is cool. Also has Nvidia drivers. If those aren't your main concerns, OpenBSD is probably better.
 
European typing detected.

GPS isn't that hard, one Raspberry Pi, one POE hat, one GPS module, one exterior waterproof box to house the pi, one GPS antenna wired to said box, one POE cable to power said box.

At the very least setup your router and file server as local NTP servers slaved to the Internet and then point all your devices at them so you don't have every single device on your network going out to the Internet for time service.
 
Theory-first analysis: Bespoke package manager, NIH symptoms. Might work great. IDK. Another interesting data point to watch, given how Xorg features in its Technologies list ( https://getsol.us/solus/technologies/ ). Interesting dependency-focused build system. Solbuild seems neat. They write a lot of code in Go. Budgie is written in Vala, the weird GTKObject-based language.

Seems a sensible choice for someone who likes Mint, but rough edges will be weird to solve because it's not "like" most other distroes. No idea how readily you'll find them. Project gives a very polished, consistent vibe, devs seem like they're not resting on their laurels.
Playing around with it in a VM it does let me run the apps I use regularly and generally looks slick, I think I'll try installing it and see how it goes.

can i rsync /home to a different drive and rsync -avP it back after installing? if my main drive is a 500GB NVMe drive should i just partition it so that / only gets 50gb and the rest of the drive is a /home partition so i don't have to migrate all the time? with Linux Mint only 33gb of my / drive is not in /home and there's a Solus.gcow2 file but the file size doesn't add up properly with disk usage
 
Back
Top Bottom